Database Users

Few solutions to problems while unbricking your Lumia

First Things First
1.This guide is highly based on the reference guides below (You should take a look there first) and is intended for those who are experiencing failures while unbricking their devices.
2.This guide only applies to black bricks (No display, no vibrant after pressing power, displaying QHUSB_DLOAD / QHUSB_BULK / QHUSB_ARMPRG in device manager). If you can still feel a vibrant after pressing power button or the NOKIA logo still displays, what you need is flashing your firmware again using Windows Phone Recovery Tool or Nokia Care Suite.
3.Thanks to these guides that I used for reference! They helped me a lot!
https://docs.google.com/document/d/1FdTtfRcR80qnSzjHX1kvTcjMRcoWh8j5hUxw8UM_prE/edit?pli=1
http://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
4.I’m new here, so please accept my apology & tell me if I’ve done anything offensive. [emoji28]
Possible ways to solve your problem with thor2
Please remember to reset your dead phone (long press power button 30 seconds) after any failed operations with thor2, or it may say “Message send failed with error code -1” while detecting devices.
1.THOR2_ERROR_CONNECTION_NOT_FOUND
Error code 85030
First try pressing the power button of your phone for 30 seconds to reset it & try again.
If that doesn’t work, it means driver not correctly installed or device not found.
Try reinstall the emergency driver here:
And then press the power button of your phone for 30 seconds.
2.THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECIEVE_FAILED
Or error code 85021
Probably means incorrect HEX file / mbn file.
*Some hex file from WPRT Server seems to be incorrect. It happens to my RM-994 (Lumia 1320), please use the hex files from the original post.
3.SAFE hex file was used and unallowed memory address was being written
Error code 85034
& SOME OTHER ISSUES.
//You could follow the instructions below if you have tried everything but still failed with thor2:
In the original post, it says that it PROBABLY means bootloader flashed, BUT I don’t really think so, because mine keeps unconscious after resetting. But I suppose, if you are seeing this, it at least means the hex & mbn files ARE CORRECT (even if it tells you to reset the device and use the correct hex file).
Now, you need to follow these steps:
1.Download Windows Phone Recovery Tool
2.Install it
3.Launch it, and click My phone was not detected.
4.Connect your phone.
If your device model could be identified successfully, it would save a lot of effort. Just follow the instructions provided by WPRT.
If it shows that “This device cannot be recovered”, you’ll need to:
1. Download your phone’s firmware (full, not only ffu).
2.Copy them to C:\ProgramData\Microsoft\Packages\Products\RM-XXX
Create the directory if it does not exist.
3.Relaunch Windows Phone Recovery Tool and click “My phone was not detected”, then you shall see your device model on the list, just simply follow the instructions and move on. (It will download hex / mbn from Microsoft Server and save your phone automatically. Those hex & mbn files will be placed in the same folder where you’ve just copied your firmware to.)
However, seems that I’ve got a really bad luck. It fails everytime when I tried to do the operation above. If you fail too, try these steps to see the log:
1.Open Settings menu in Windows Phone Recovery Tool.
2.Select Troubleshooting and export your log file.
3.Open your log file and search for “thor2.exe -mode emergency –hexfile”.
4.You’ll find a sentence around it showing where the log file of thor2 is stored.
Mine’s like this:
SEE ATTACHMENT
Open that log file you’ll see what the heck has happened then check up the error code at the beginning part.
If it shows error code 85021, you’re probably experiencing the same issue as me:
The solution to that is simply copying the command in that log file and change the hex file & mbn file into your own ones from xda and then execute it in command prompt. Finally, the NOKIA logo appeared on the screen of my device and I got pumped.
This is the first time for me to write such guides, so it might not be clear in someways. This guide is somewhat based on the guides I've referred to, and I really appreciate those great contributors (and you may also want to read their original post to learn more ).
Wish all you guys good luck.

That might be helpful incase I totally brick my phone, which... never will happen.

Great Thanks!
Sent from Board Express on my Nokia Lumia 1020. Best phone ever!!
Note to noobs: DON'T PM ME WITH QUESTIONS. POST IN THE FORUMS. THAT'S WHAT THEY ARE HERE FOR!

If your device model could be identified successfully, then lucky you.  Just follow the instructions and everything will be fine.
If it shows that “This device cannot be recovered”, you’ll need to:
1. Download your phone’s firmware (full, not only ffu).
2. Copy them to C:\ProgramData\Microsoft\Packages\Products\RM-XXX
Create the directory if it does not exist.
3. Relaunch Windows Phone Recovery Tool and click “My phone was not detected”, then you shall see your device model on the list, just simply follow the instructions and move on. (It will download hex / mbn from Microsoft Server and save your phone automatically. Those hex & mbn files will be placed in the same folder where you’ve just copied your firmware to.)
this worked for me !
then flashed manually via thor2 :
thor2 -mode uefiflash -maxtransfersizekb 128 -ffufile “C:\ProgramData\Nokia\Packages\Products\rm-XXX\rest_of_path_to_file.ffu“

I have a Lumia 830 RM-983. I have tried re-flashing my phone 5 times now. Nothing is working!

jimmy19990 said:
If it shows that “This device cannot be recovered”, you’ll need to:
1. Download your phone’s firmware (full, not only ffu).
2.Copy them to C:\ProgramData\Microsoft\Packages\Products\RM-XXX
Create the directory if it does not exist.
3.Relaunch Windows Phone Recovery Tool and click “My phone was not detected”, then you shall see your device model on the list, just simply follow the instructions and move on. (It will download hex / mbn from Microsoft Server and save your phone automatically. Those hex & mbn files will be placed in the same folder where you’ve just copied your firmware to.)
Click to expand...
Click to collapse
it's worked for me, thanks

i love you man i fixed my phone

https://forum.xda-developers.com/windows-phone-8/development/unbrick-dead-boot-lumia-jtag-t3872885

unbrick LG G2 Force Flash with Send_command.exe

Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed

Thank you guy, your tuto saved my device
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse

help please
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.

sms473 said:
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
Click to expand...
Click to collapse
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?

santatralalaina said:
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
Click to expand...
Click to collapse
Hi..thanks for the reply....My phone is G2 F320L..Korean version with removable battery and SD card....I tried to install a non compatible ROM..got bricked with only fastboot...Then I try to flash aboot.bin..boot.bin..laf.bin..etc files (which I have extracted from the kdz) through fastboot...during flashing my phone was disconnecting and connecting back again...thats where all the problem started I guess. Now I dont have fastboot also. If i connect my phone to PC.. LG logo comes on the phone screen...on PC it try to detect as LGE android MTP devices and try to install the driver of the same. But the driver installation fails eventually.... At windows device manager it show as LGE Android MTP devices with error code 10...and showing connected to port:COM3....If I try to get in to the download mode..it get stuck at the (.............) download page...it is not going to the page with big USB picture...
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?

sms473 said:
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
Click to expand...
Click to collapse
Hello,
It was easy to unbrick the fastboot but now... ok, you are stuck in LG LOGO but after no black screen? can you charge you battery? And if you try to go to RecoveryMode, what's happen? do you have multiple partitions and QHSUSB_DLOAD trying to be instaled? It's also easy to unbrick the QHSUSB and if it is the case, don't use send_command to flash manualy your device.
Maybe, you can force flash. You have to find a solution to push all .img files to your device. If you cannot use ADB, try to put the img files to sdcard.
you can found send_command.exe and ports.bat in this zip file, it's an utilities for having root on LG G2 :
LG_Root.zip
you can use all root command with it!

Added to index thread
[INDEX][LG G2] ROMs, Kernels, Guides and more

can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time

Well, I need help. how do i copy these files to my device? my device is not located in adb. cant i just flash the files from there place in my pc?

hi - I have t mobile d801 .it has boot loop - show lg logo and then the android robot and then lg logo again.
it does enter download mode(but with the 4 blue dots - but in the device manager cant install the drivers.
when the phone is plugged in to computer normally without download mode' it shows lge phone and drivers in device manager.
I tried to flash kdz bit stuck on 60%. it shows on phone download mode - but not show the firmware update logo.
what should I do?? when I d.mode not the regular d.mode - device isn't detected in pc. so I think this is my main problem.
try with srk tools no luck. its says waiting for device..is there any solution? thanks!

foxyfoxyblah said:
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Click to expand...
Click to collapse
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)

santatralalaina said:
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
Click to expand...
Click to collapse
I don't have ADB, so most of these i cant do.
im scared of touching the motherboard....
so im not shorting test point.

santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
i have flashed wrong firmware ..now my phone have same symptoms like urs with partial download mode and no recovery....but i m unable to push files via adb bcz adb debugging is not active and i m getting error that phone not found.....now what can i dooo...plz plz plzzzz help me

I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else

santatralalaina said:
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
Click to expand...
Click to collapse
and how to do that?

Thank you your topic was helped me to find a solution for my phone lg g3

How to fix imei problem on lenovo k8 note

Requirements :
1) Maui Meta Tool : DOWNLOAD HERE
2) MediaTek USB Vcom Drivers : DOWNLOAD HERE
3) Windows 7 PC ( Recommend )
Instructions :
1) Download USB driver zip, extract it and install the drivers on your Pc. (Ignore if already installed)
2) Download Maui Meta tool and Unzip it using 7zip or any other extracting software.
3) Open Maui Meta application as administrator.
4) Wait till the application dashboard appears.
5) Under connection type, Choose Smartphone.
6) Click Reconnect button at the top.
7) Now Switch off your android phone and connect it with your PC via USB Cable then Power On.
8) When the circle color change to yellow, it means that your phone successfully detected and your device will stuck on Boot logo. ( Maui Meta mode ).
9) Now Click on the Get Target Version to confirm your phone.
10) Your phone details appear.
Come back to the main dashboard of Maui Meta.
11) Choose iMei Download option from the dropdown menu.
12) IMEI Download box should be open in new tab. Click on Change NVRAM Database File.
13) In the new tab window, choose the path of BPLGUInfo file (often named like BPLGUInfoCustomAppSrcP_MT67**…), select it then click Open.
NOTE :
a) Use database from the same firmware version of your current ROM.
b) The database will locate at K8 Note Stock ROMs folder under diagnosis folder.
c) Under diagnosis folder extract modemdb zip to any place.
d) The required file is MDDB_InfoCustomAppSrcP_MT67**... Under manning_lwgdsd folder.
14) Now, enter the first 14 digits of the IMEI you wish to write. The digit entered in the CheckSum box will be the 15th digit of the IMEI.
15) Then click Download To Flash (If IMEI keeps disappearing after factory reset then try clicking Upload From Flash instead)
16) After successfully write iMei number for your device, you should see a message at the bottom saying Download IMEI to flash successfully.
17) Now click Disconnect button on Maui Meta and your device will switch off.
Done.
Tips: If your device can't Boot into Maui Meta mode, flash Stock ROM again with Format All + Download mode with SP Flash Tool. This error can happen if device was rooted or installed custom recovery.

[GUIDE][UNBRICK] The Huanor GR5X fully unbrick guide

Hi mates, today i come with the unique guide for unbrick our Huanor GR5X phones
THIS GUIDE IS FOR FULLY BRICKED HUAWEI GR5/5X HONOR, ALL MODEL/VARIANT
ATENTION!!!
Files rawprogram0.xml and patch0.xml from my packcage its ONLY for the Huawei GR5 KII-L23 16GB VARIANT!!!
In order to continue with the tutorial, you must create your rawprogram and patch0 xml files
(mini tutorial bellow)
Ready? GO
1) Download my packcage (link MEGA)
2) Install QFIL Software. From my packcage, extract and move the folder 'Firmware' to C:\Program Files\Qualcomm\QPST\bin
3) Download and extract this .IMG files from ANY 5.1 full firmware UPDATE.APP for your model/variant
(Note: for KII-L23 is not necessary GPT.img)
GPT.img
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
Place all img files in C:\Program Files\Qualcomm\QPST\bin\Firmware
4) Install Qualcomm drivers, Connect phone to pc, open Device Manager. If you see under com port Qualcomm USB loader or something along those lines. your good.
5) In QFIL software, if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008 (if say 9006,900E, you must put your phone into EDL mode with EDL Cable or EDL TEST POINT, google it)
6) Once you get the Qualcom USB loader 9008 on QFIL, you can continue
6) Select Build Type: click Flat Build
7) Select Programmer: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware\prog_emmc_firehose_8939.mbn and select
8) Load XML: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware and select "rawprogram0.xml" file, then select "patch0.xml" file.
9) Go to Tools and click Partition Manager
10) You will see a list with all files from partition table
11) To flash, you need select Boot.img in the list first, a mini windows will open, click on Load image and select the Boot.img placed on C:\Program Files\Qualcomm\QPST\bin\Firmware
Do the same with the rest of img files in THIS order
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
12) Once you finish, close the partition manager. A message will appear and phone will reboot. If not, reboot manually
That's all enjoy!
FOR GR5 KII-L2X AND HONOR 5X KIW-L2X MODEL/VARIANT, FOLLOW THIS TUTORIAL
1) Download my packcage and exctract it
2) Open a cmd windows in 'Phyton + GPT Tools' folder
3) Type: GPTAnalyzer.py (drag and drop the GPT.img file previously downloaded from 5.1 firmware) and click Enter
4) Copy all results in cmd, paste on notepad and save as 'Partition0.xml' (start with <?xml version... and finish on </configuration>)
5) Type GPTParseTool.py -x (drag and drop the partition0.xml created) and click enter
6) Go to phyton folder and move all created files to C:\Program Files\Qualcomm\QPST\bin\Firmware
7) Now you can continue with the guide
Thats all my friends, hope you get a new life for your Huanor GR5X
PLEASE IF I HELP YOU, BUY ME A COFFE HERE

Reserved

GOOD guide！someone will need it！
my question：does it work on the locked phone?

wsdyleon said:
GOOD guide！someone will need it！
my question：does it work on the locked phone?
Click to expand...
Click to collapse
Thanks!
Locked and unlocked devices.

My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.

faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
I cant find python + GPT tools

faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc

Ibrahim Tariq said:
I cant find python + GPT tools
Click to expand...
Click to collapse
Here you will find all files needed and instructions
You have to open the phone and put it in EDL mode
Search Google for that
https://forum.hovatek.com/thread-31505.html

snazzyman89 said:
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.
Click to expand...
Click to collapse
Ibrahim Tariq said:
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
Click to expand...
Click to collapse
See my reply in previous post #8
---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------
Can't we use Huiye Download Tool to flash all the images ?

what if i dont have system.img in my firmeware ? what should i do ? i have firehose from b321 can this be compatible with b330?
EDIT : i found the sys.img for b321

friends help me out i have KiW L21 superbricked unable to charge battery and he dont show up in device manager as qloader 9008

Possible way to unbrick a hard brick device with lock bootloader . (Not working)

Disclaimer :
I'm not responsible for bricked devices, dead SD cards. This guide have not tested by anyone yet and because of that have a high chance to damage your device .Please think twice before deciding to do this guide !!!
Hello all, I was successful to extract the ofp firmware for the CN and GLOBAL version. The firmware is kind of QFIL based firmware and include patch0.xml , rawprogram0.xml , prog_firehose_ddr.elf that can be loaded on the Qualcomm QFIL tool for flashing a stock rom on EDL mode .
I do not have this phone yet so this is not tested by me but it should work .
This should work on bricked devices with locked bootloader .
This is not a full guide as I haven't tested it yet, but I will share you of my idea. I suggest to not try this if your not in hard brick and the bootloder is not locked .
Warning- This process will wipe your internal storage .
1. Extract the firmware and the 1-Qualcomm USB Driver + QFIL.7z.
2. You should install the Qualcomm USB Driver
3. Install QPST.2.7.480 , move the firmware to C:\Program Files (x86)\Qualcomm\QPST\bin .
4. Run as administration the QFIL software ,it found on C:\Program Files (x86)\Qualcomm\QPST\bin .
5. Click on the Configuration tab and then on the FireHose configuration .
6. Click on the Device Type and choose ufs .
7. Tick the "Reset after Download" and press OK.
8. Tick the flat boot circle option .
9. Click Browse on the Programmer Path and choose prog_firehose_ddr.elf in the firmware file .
10. Click Load XML and choose "rawprogram0.xml" and then choose "patch0.xml" .
Open windows device manger, boot you phone to EDL by connecting a cable to you PC and then press and hold power bottom and volume + bottom .You should see Qualcomm HS-USB QDLoader 9008, It is really important to be on QDLoader 9008 .Do not try to proceed to 11 if it does not show as QDLoader 9008 .
11. you will see the Port on the QFIL software and then choose Download .
Download -
Qualcomm USB Driver + QFIL - https://mega.nz/file/pU8FRILJ#y54f4lnq6p3T7TCITGyWRw0Kuf4ymgOt4srQ654NqUo
Extracted RMX1931EX_11_A.09 OFP (Global firmware) - https://mega.nz/file/YQ80wSwB#wflYZ-hI5O96QjTq4oc4pnovn6UoAtry2lHn7ThmbLo
CHECK MD5 !!! - 58A5C6D75787029B664FD5583F265872
Extracted RMX1931_11_A.11 OFP (CN firmware) - https://mega.nz/file/lMMlQK4K#bOCrQrg7tkKj2n6VNhS__4bBQw1RdsxTSI5XrzRpMG0
CHECK MD5 !!! - A0CCED006DF8FC0B06B0669A8325883F
Please download the firmware according to your realme x2 pro model, This probably wont work and may damage your device if you have a CN model and try flash a EU firmware and the opposite EU model and try flash a CN firmware .
UPDATE-
After long testing it seem that we can not write to or read from this phone without the realme tool, It must have a special code . I will stop searching for a way because it seems impossible without the Realme tool.
Thanks to @shilpakar7, @Designguru and @iamkgehlot for testing tools and files for many hours .
English is not my native language, please excuse any errors on my part.

Reserved

Fingers crossed ? if it works, it's going to help alot of folks!

luisarriaga said:
Fingers crossed ? if it works, it's going to help alot of folks!
Click to expand...
Click to collapse
Yes I know, It also will remove the fear of hard brick when locking the bootloder .
Furthermore if it will work for the realme x2 pro, it will work on many Realme devices that have a snapdragon CPU including the realme x2 .I just need to extract the ofp firmware of each device .

Yes absolutely! It's the only android smartphone I never unlocked the bootloader, first of all because of loosing FP if you install twrp, and there's the risk of relocking it. Let's wait for some feedback ?

Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail

Designguru said:
Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Click to expand...
Click to collapse
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?

or965 said:
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?
Click to expand...
Click to collapse
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)

Designguru said:
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)
Click to expand...
Click to collapse
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin

or965 said:
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin
Click to expand...
Click to collapse
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------

Designguru said:
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .

or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")

what about using qpst tool as mentioned in https://www.getdroidtips.com/stock-rom-realme-x2-pro/ Method 3. The above mentioned url contains guide for chinese ROM but since you have ofp firmware for global version. Will this method work?

it fails during dowload process. I have attached the log.
Total to be tansferd with <program> or <read> is 8.98 GB
09:09:35: INFO: Sending <configure>
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26'
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26
'
09:09:35: INFO: TARGET SAID: 'INFO: Chip serial num: 1387265276 (0x52affcfc)'
09:09:35: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
09:09:35: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
09:09:35: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Writing log to 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download

or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.

tsongming said:
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.
Click to expand...
Click to collapse
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
And here is my log from C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_5 port_tra
ce.txt
https://pastebin.com/2VynsCD7

shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse

ok thank you for your advice, I will definitely take it as a reminder. I have uploaded the log file to pastebin.com and postel the url link. Since you don't personally have the device, I shouldn't have asked for more help. Anyways thank you for your valuable time. Since this is so frustating, I guess i will just send it to service center for repair.
tsongming said:
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Designguru said:
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
Finally said:
@or965[/user] stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Click to expand...
Click to collapse
I did not have this device yet so I do not successfully restored my phone .

or965 said:
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
I did not have this device yet so I do not successfully restored my phone .
Click to expand...
Click to collapse
this method also not working. The status tab on MiFlash displays same message as mentioned by designguru