Related
I flashed my GT540 to the official Eclair update, now i want to flash the fastboot-enabled version over this, but when i run the KDZ_FW_UPD.exe and select the V20B_00+fastboot.kdz file and 3GQCT, nothing happens, i guess because the drivers aren't correct.
i have tried several different drivers like
LGAndroidDriver_WHQL_ML_Ver_1.0_All_Win7.exe
(i am in Windows 7 64-bit) nothing is working.
this is the output
Code:
[R&D Test Tools Log File]
11:00:04 : Launching SW update
11:00:04 : Unpacking KDZ
11:00:06 : KDZ file extraced
11:00:09 : Files were extracted.
11:00:09 : LGMobileDL Load.
11:00:09 : Port = -1
11:00:09 : Connecting to phone
11:00:09 : PHONE WAS NOT FOUND!
11:00:11 : ===FINISHED===
edit: i have rooted this using z4root, if thats any help
what i want to do is get some swiftdroid/CM on the phone.
basically i need to know what the correct working drivers are. someone must know.
edit 2: nvm found out why the drivers weren't recognising it, the stupid MASS STORAGE ONLY option was enabled, in SD CARD AND PHONE STORAGE. try turning this off if you're having problems.
Greetings Everyone;
Like many of you: my Lumia was not working properly; therefore I tried to recover / downgrade my Lumia 535 with "Windows Phone Recovery Tool" back to Windows 8.
After Clicking "Start"... The Phone simply said: "Goodbye" and never came On again... (While going like: "WT*!?" and mad at this; I have to say it was funny).
From that point on: It simply would just show a Black Screen to me.
Requirements
- Have Windows Device Recovery Tool ("WDRT") (Get it here)
- Make sure you have a USB Cable in proper condition to ensure that the Procedure Won't Fail due to Disconnection.
Method #1 : Before Anything Else
1 ) With your USB Cable & Device Connected to PC; Go to the "Device Manager" and unninstal the QHSUSB__BULD Driver (Don't Close the Device Manager Yet).
2) Disconnect your USB Cable and Plug it again. Update the "Device Manager" in order to get your QHSUSB__BULK Driver Installed again.
3) Go to "Windows Phone Recovery Tool" and try Again. "Windows Phone Recovery Tool" should be able to complete the procedure.
Method #2 : Under "Emergency Mode"
1 ) Connect your device via USB cable.
2) Open the following folder (Considering your System drive is " C: ")
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.
If you don't find the *.ffu file there you can try: http://www.lumiafirmware.com/
3) Now open CMD (Command Prompt) as administrator
4) And go to WDRT folder by typing:
cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
for 32 bit pc, type:
cd C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool\
5) Connect your USB Cable & Device to PC
6) (Attempt to Perform a Factory Reset): In CMD (Command Prompt) Type :
thor2 -mode uefiflash -ffufile "C:\the location of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset"
7) Wait now until your phone gives a green screen
8) Back on CMD; Type:
thor2 -mode rnd -bootnormalmode
Note: Shall Step 6 fail; but you managed to flash the *.ffu file into the device (or even if that failed); try Method #1 again.
That worked perfectly for me.
Initial Steps for Manual Recovery (Incomplete; but gets you Started)
1) "dump": "gpt0.bin" & "gpt1.bin" files
2) Create a Folder on the root of your System Drive.
i.e: C:\LumiaService\
3) Create another Folder Called "Dump" inside "LumiaService" folder
4) Copy the *.ffu File found at: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
to the Newly created folder [C:\LumiaService\ ]
Tip: You may want to rename the file to a shorter file name. In this tutorial I'm going to name it "rm1089.ffu" (Wich stands for my Lumia Model)
5) Open Command Prompt in Administrator Mode and Open the "Windows Phone Recovery Tool" folder.
i.e: C:\ThisComputer\User\Programs (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
Note: There you should find: Thor2.exe
6) Once in that folder type the following Command to "Dump" (Extract from & Create) the following files: gpt0.bin & gpt1.bin
Note: Don't Close your Command Prompt Window After Dumping the Files (See point 6).
thor2 -mode ffureader -ffufile "C:\LumiaService\rn1089.ffu" -dump_gpt -filedir C:\LumiaService\Dump\
7) Copy the RKH Hex Number and Save it into a text document (Pref. also inside "LumiaService" folder)
i.e:
RKH: 0E9427DF118D9E27D098D13BECB6C6C89CE59F4
RKH: 0E9427DF118D9E27D098D13BECB6C6C89CE59F4
Note: You will require to create a *.hex File using the RKH; in order to Perform the manual Unbrick.
Hope this helped everyone guys without warranty.
If you still have problems; and want to dig further into Manually Unbrick I'm leaving some of my own notes on the post bellow (For Reference Only).
I think that would be a good starting point; and that it will save you some time.
Please feel free to send me information regarding how to do it "Manually" (Step-by-Step); I'll be glad to write about it.
Best Regards;
Reference For Manually Unbrick
Thor2 Boot Modes
Boot to System
thor2 -mode rnd -bootnormalmode
Boot Into Boot Manager
thor2 -mode rnd -bootlumiabootmgr
Emergency Mode
thor2 -mode rnd -boot_edmode
USB MSC Mode
thor2 -mode rnd -bootmsc
Needless to say that you can check thor2 help file with:
thor2 /?
Problems with the *.hex File:
People who have a problem with the hex file, is because the hex file is invalid. The converter tool does not do a good job with converting bin files which are bigger than 64 KB.
To demonstrate: look at the file size of the original bin-files. Some are 60 KB and some are 74 KB. The conversion of the files with size 74 KB fails.
Look at the output hex-file in Notepad++.
Scroll to line 4098. From there on you see that all lines have an extra character. There is an odd number of digits, which is not possible with hex-values.
How to correct it?
Insert this line at linenumber 4098:
:020000042A01CF
All the next lines, except the last 3 lines start with:
:101
Replace that with:
:10
The last 3 lines should not be changed.
Save the hex-file and it will be ready to use.
Note: That line must be put at line 4098. And everything below will go down one line. Look at the lengths of the lines. In the original hex-file all lines from 4098 and below have an extra character. That is wrong. To go beyond the 64 KB limit, this extra line is needed and then the bad characters from the lines below must be removed as described.
Addittionaly:
1. The bin files in your opening post are fine, but they are probably incomplete. There are Lumia models, which have the same RKH, but they need different MPRG's. Not much we can do about now.
2. The bin files are converted to hex files. Those hex files are in your opening post. But not all of them are correct. I corrected a few of them and those are in post #76. You probably want to update the files in your opening post with these files.
Info
Tutorial it is not a complete step-by-step.
You need to sign everything as does .vpl programming (All recovery/flashing tool uses .vpl flashing).
1. Direct write .FFU will work as MSFT.
2. Writing with .Vpl file will work as OEM.
It is all same thing, but try to understand between two diff things.
Some security will get tight or can be vulnerable. (Actual I mean, OS will run with more differential)
How to get *.hex file
1) Get "bin2hex" Console Application
2) In Command Prompt go to your Bin2Hex.exe location and Copy your *.bin file there.
3) Type: bin2hex myBinFile.bin MyNewHexGile.hex
i.e: 00E9427DF118D9E27D098D13BECB6C6C89CE59F4.bin HEX.hex
The application will create the *.hex file for you.
Note: There's a chance that the new *.hex file could not be perfectly converted.
Check: Addittional Reference > Problems with *.hex files on this post (above).
Tip #1:
Use this extra FLAG in order to prevent the device to fail receiving the files through "Thor2":
-maxtransfersizekb 256
*Note: Some people reported that this value can be too high and cause flashing issues
XDA Links
Title: "Finally... unbrick your Lumia device QHSUSB_DLOAD without JTAG"
Title: "Qualcomm/Intel HEX files"
Title: "How to recover a Lumia with a malfunctioning USB port"
Hello!!! I have a problem. I can't find my device as QHSUSB_BULD. What I can do? I am desesperate
recover data
boris_urgiles said:
Hello!!! I have a problem. I can't find my device as QHSUSB_BULD. What I can do? I am desesperate
Click to expand...
Click to collapse
Is it possible to recover data from a damaged lumia?
I made a program that make this a lot easier
rgxHost said:
Greetings Everyone;
Like many of you: my Lumia was not working properly; therefore I tried to recover / downgrade my Lumia 535 with "Windows Phone Recovery Tool" back to Windows 8.
After Clicking "Start"... The Phone simply said: "Goodbye" and never came On again... (While going like: "WT*!?" and mad at this; I have to say it was funny).
From that point on: It simply would just show a Black Screen to me.
Requirements
- Have Windows Device Recovery Tool ("WDRT") (Get it here)
- Make sure you have a USB Cable in proper condition to ensure that the Procedure Won't Fail due to Disconnection.
Method #1 : Before Anything Else
1 ) With your USB Cable & Device Connected to PC; Go to the "Device Manager" and unninstal the QHSUSB__BULD Driver (Don't Close the Device Manager Yet).
2) Disconnect your USB Cable and Plug it again. Update the "Device Manager" in order to get your QHSUSB__BULK Driver Installed again.
3) Go to "Windows Phone Recovery Tool" and try Again. "Windows Phone Recovery Tool" should be able to complete the procedure.
Method #2 : Under "Emergency Mode"
1 ) Connect your device via USB cable.
2) Open the following folder (Considering your System drive is " C: ")
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.
If you don't find the *.ffu file there you can try: http://www.lumiafirmware.com/
3) Now open CMD (Command Prompt) as administrator
4) And go to WDRT folder by typing:
cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
for 32 bit pc, type:
cd C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool\
5) Connect your USB Cable & Device to PC
6) (Attempt to Perform a Factory Reset): In CMD (Command Prompt) Type :
thor2 -mode uefiflash -ffufile "C:\the location of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset"
7) Wait now until your phone gives a green screen
8) Back on CMD; Type:
thor2 -mode rnd -bootnormalmode
Note: Shall Step 6 fail; but you managed to flash the *.ffu file into the device (or even if that failed); try Method #1 again.
That worked perfectly for me.
Initial Steps for Manual Recovery (Incomplete; but gets you Started)
1) "dump": "gpt0.bin" & "gpt1.bin" files
2) Create a Folder on the root of your System Drive.
i.e: C:\LumiaService\
3) Create another Folder Called "Dump" inside "LumiaService" folder
4) Copy the *.ffu File found at: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
to the Newly created folder [C:\LumiaService\ ]
Tip: You may want to rename the file to a shorter file name. In this tutorial I'm going to name it "rm1089.ffu" (Wich stands for my Lumia Model)
5) Open Command Prompt in Administrator Mode and Open the "Windows Phone Recovery Tool" folder.
i.e: C:\ThisComputer\User\Programs (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
Note: There you should find: Thor2.exe
6) Once in that folder type the following Command to "Dump" (Extract from & Create) the following files: gpt0.bin & gpt1.bin
Note: Don't Close your Command Prompt Window After Dumping the Files (See point 6).
thor2 -mode ffureader -ffufile "C:\LumiaService\rn1089.ffu" -dump_gpt -filedir C:\LumiaService\Dump\
7) Copy the RKH Hex Number and Save it into a text document (Pref. also inside "LumiaService" folder)
i.e:
RKH: 0E9427DF118D9E27D098D13BECB6C6C89CE59F4
RKH: 0E9427DF118D9E27D098D13BECB6C6C89CE59F4
Note: You will require to create a *.hex File using the RKH; in order to Perform the manual Unbrick.
Hope this helped everyone guys without warranty.
If you still have problems; and want to dig further into Manually Unbrick I'm leaving some of my own notes on the post bellow (For Reference Only).
I think that would be a good starting point; and that it will save you some time.
Please feel free to send me information regarding how to do it "Manually" (Step-by-Step); I'll be glad to write about it.
Best Regards;
Click to expand...
Click to collapse
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)
https://forum.xda-developers.com/windows-phone-8/development/unbrick-dead-boot-lumia-jtag-t3872885
H
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
It support QHSUSB_BULK?
fadilfadz said:
H
It support QHSUSB_BULK?
Click to expand...
Click to collapse
Firstly you need to switch to QHSUSB_DLOAD mode.
There are some guides on the internet, search for it.
gmirz2005 said:
Firstly you need to switch to QHSUSB_DLOAD mode.
There are some guides on the internet, search for it.
Click to expand...
Click to collapse
Where? I can't find it on google.
Give me just url.
fadilfadz said:
Where? I can't find it on google.
Give me just url.
Click to expand...
Click to collapse
Alright.
So firstly fully uninstall all drivers.
(Nokia Emergency Connectivity, QHUSB_DLOAD, QHUSB_BULK)
Now disconnect the battery, if the battery is "non-removable" then dissasemble the back cover and disconnect the battery.
Now wait for 1 minute while holding the power button of your lumia (to fully drain power).
Reinsert the battery and connect it to the computer.
You should see a driver installing
"Qualcomm ++++"
Now goto WDRT
Select "My phone is not detected"
Click LUMIA
If WDRT recognized the device, you should see it.
If not then repeat all the steps as much as WDRT will finally detect.
Click the device
Start recovery process.
Done!
Ffu not signed for this device while i'm load corrected ffu for my lumia 1020
my lumia 1020 can detected by wdrt but while processing to flashing, wdrt show error code ffu not signed for this device, any solution to fix this? my lumia detected as NOKIA BOOTMGR or QUALCOMM MSM DEVICE
faisalmm_ said:
my lumia 1020 can detected by wdrt but while processing to flashing, wdrt show error code ffu not signed for this device, any solution to fix this? my lumia detected as NOKIA BOOTMGR or QUALCOMM MSM DEVICE
Click to expand...
Click to collapse
Use the THOR2 method.
gmirz2005 said:
Use the THOR2 method.
Click to expand...
Click to collapse
I've use thor2 method and qhsusb_dload, but thor2 error code 85021 send_rcv_msg_failed, I use correctedhex, hex on gpt0.bin with bin2hex, hex on lumiafirmware, but no any hex work for my device
LOG thor2
[21:51:55.775] D_MSG : THOR2 1.8.2.18
[21:51:55.775] D_MSG : Built for Windows @ 13:36:46 Jun 16 2015
[21:51:55.775] D_MSG : Thor2 is running on Windows of version 6.2
[21:51:55.775] D_MSG : thor2.exe -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -ffufile RM875_3051.50009.1424.0003_RETAIL_apac_indonesia_1002_03_447615_prd_signed.ffu -skipffuflash
[21:51:55.775] D_MSG : Process started Mon Dec 31 21:51:55 2018
[21:51:55.792] D_MSG : Debugging enabled for emergency
[21:51:55.792] D_MSG : Initiating emergency download
[21:52:14.320] D_MSG : Using default emergency protocol
[21:52:14.320] D_MSG : ALPHA EMERGENCY FLASH START
[21:52:14.320] D_MSG : Emergency Programmer V1 version 2014.10.31.001
[21:52:14.320] D_MSG : Hex download selected
[21:52:14.320] D_MSG : Check if device in Dload
[21:52:14.323] D_MSG : Connection to DLOAD mode succeeded
[21:52:14.323] D_MSG : Get Dload parameters
[21:52:14.811] D_MSG : Sending HEX flasher to the device
[21:52:14.823] D_ERR : Sending HEX flasher to the device failed. Try to re-send.
[21:52:16.826] D_MSG : Re-sending HEX flasher to the device
[21:52:17.829] D_ERR : Message send failed with error code -1
[21:52:17.830] D_ERR : Cannot upload HEX flasher into the device
[21:52:17.830] D_MSG : Sending GO command if HEX flasher successfully uploaded.
[21:52:18.327] D_MSG : ALPHA EMERGENCY FLASH END
[21:52:25.851] D_MSG : Emergency messaging closed successfully
[21:52:25.935] D_MSG : Operation took about 30.00 seconds.
[21:52:25.969] D_ERR : THOR2 1.8.2.18 exited with error code 85021 (0x14C1D)
Click to expand...
Click to collapse
faisalmm_ said:
I've use thor2 method and qhsusb_dload, but thor2 error code 85021 send_rcv_msg_failed, I use correctedhex, hex on gpt0.bin with bin2hex, hex on lumiafirmware, but no any hex work for my device
Click to expand...
Click to collapse
If you have the original FFU for your device, try re-downloading it and re-extracting the .hex and .mbn files
this may work...
Hi,
I have a Lumia 1020 that was running Windows 10 Mobile thinking it was a Lumia 950 XL. With this week's update, it broke and is now showing an error message "Unable to find a bootable option".
I've tried unlocking the Bootloader with WPInternals and it doesn't work (I've tried with original FFU and with L950XL FFU).
Windows Device Recovery Tool also doesn't work (it identifies a device although it doesn't name it and proceeds into the reset but stops with an error message of "Software not connected or disconnected from device").
I can't find any drivers on device manager like the ones you mention and the command line way always returns an error: 0xFA001106.
I really don't want to give up this yellow phone. I love it.
Can somebody please help?
Thank you.
Edit: the device shows up as Nokia BootMGR and it's always stuck in a "unable to find bootable option. Press key to shutdown" loop.
I just thought of something else: when I installed W10M on my Lumia, I changed it to make it appear as a Lumia 950XL. I used InterOP tools and RegEdit. Could this be related to the FFu signature problemas I'm getting today? How would I change these values?
WPInternals info: https://1drv.ms/u/s!Ag-KZVVb9pL6q5pd7wcC32KiUZzfjQ
My phone is booting to QHSUSB_BULK and i have error with thor2 commands
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode rnd -bootmsc
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 rnd -bootmsc
Process started Fri Sep 23 13:10:45 2022
Logging to file C:\Users\grego\AppData\Local\Temp\thor2_win_20220923131045_ThreadId-23132.log
Initiating do RnD operations
WinUSB in use.
Debugging enabled for rnd
Detecting UEFI responder
Device is not in Lumia UEFI mode
Reading device mode failed
THOR2_ERROR_UEFI_RESPONDER_DETECTION
THOR2 1.8.2.18 exited with error code 84017 (0x14831)
Installing the H815 Nougat Stock [v29A] on the H818P.
5.1 Installation
1 - Download KDz from 5.1;
2 - Put the phone in download mode and open the LG UP;
3 - Load KDz into the program and start;
4 - I hope to connect, configure and depart for the next procedure.
Root process
1- Download all files;
3 - Download IMG from the V10C BRASIL system or V10D Brasil (check the version of your software), after downloading and downloading the IMG to the internal memory of the device.
4. Install the drivers (if you do not have one) and extract the LG_Root.zip to the LG Root folder;
5- On the device, enable USB Debugging in the Developer Options;
6- In the LG Root folder, right-click pressing shift and click Open Command Window here.
7- Connect the USB cable to the computer and allow debugging;
8- In the open command window type adb.exe devices, so if the device is connected the computer will inform in the window. Example: List of devices attached, LGH818P (letters and numbers), device;
9- Disconnect the USB cable and the device. With it off, press the volume more, plug into the USB port, the device will turn on Download Mode;
10- Go back to the folder, with the device already in Download Mode, double click on the Ports file, it will open another command window, copy the port number that appears in \ Device \ LGANDNETDIAG1 REG_SZ COMxx, note the xx because it is the number of the door, write down the number, then close the window that has been opened;
11- Go back to the command window that you had previously opened, in it copy and paste the command Send_Command.exe \\. \ COMxx and change the xx by the number of its port;
12- Still in the window, type id, a message will appear. Example: uid = (0) root gid = (0) root. If it does not, type again;
13- It's time for root, you should be sure now that you have copied the correct port and that the file from step 2 is in the internal memory. Enter the command
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
and hit Enter on your keyboard. It should take about a minute, wait until # appears.
14- After you finish, type LEAVE for your device to reboot. Root is done.
Installing Nougat
1 - Right after Root download the Flash Fire, and install it;
2 - Copy to rom for internal storage, compact even;
3 - Right after pressing the "+" and select the option "Flash ZIP or OTA";
4 - Ira appears to navigate the internal memory, select the rom;
5 - Then select the "Flash" option;
6 - It will restart and soon after starting the installation;
7 - Ready, now just wait;
NOTE: In the LG logo it will take a little, something from 3 to 5 minutes.
DOWNLOADS :
V10C_BRA_root.rar: https://mega.nz/#!Y1lQWDrY!ItgAfCNX7oO1XPLLS9hT3WLDi3MBQ0LOe6vPoMtut-I
V10D_BRA_ROOTED.zip: https://mega.nz/#!Ro8XVBqC!EDbYZ9weJj7Pn3ewLB9hEy6ZjGiRCX_igtt5kPZLADE
Drivers: http://www.lg.com/br/suporte/suporte-celular/lg-H818P
LG Root: https://mega.nz/#!4xNBAIiZ!TR9kHjYMaHKZLg2Fm8ceGffGTMiWSmP8Q0bBxuOkFxQ
Stock Rom: https://lg-firmwares.com/lg-h818p-firmwares/#firmwaresList
LG-H815_Official_v29A.
https://www.androidfilehost.com/?fid=817550096634794247
IF YOU WANT DOWNGRADE 7.0 TO 6.0
SEE ALL HERE
http://raspberryjuntopi.com.br/2017/10/13/off-downgrade-lg-g4-do-nougat-para-o-marshmallow/
https://www.youtube.com/watch?v=9Vk1TJ96eG4&feature=youtu.be
FILE H815 V20o Modded.kdz
you can drop from 7.0 to 6.0 and run the manual modem
The easiest way to get it manually (you need root):
Copy the IMG-file of the modem in the internal storage (do not rename it!)
on your computer, the command ADB line
Execute «adb shell» (without the quotes)
Lift the skin with the command su (again, without quotes)
Then execute the following commands:
dd if = / dev / zero of = / dev / block / platform / bootdevice / by-name / modem
dd if = / sdcard / modem_h818p_20h_gcc.img of = / dev / block / platform / bootdevice / by-name / modem
Finally, restart your phone and it should work.
modem_h818p_20g.img
https://mega.nz/#!e5snTbaL!BYplWw8MAyNFWJ0VrrA4UZjV0Ric3-RxIRUsELZjk1c
6.0
https://mega.nz/#!H8dnXDCL!hqA-yIN3dAeuqHm-H0KltL6rfTJfb0EpVcNJYkkr0GU
hi,
Can I Root & Flash that Nougat ROM on my G4 H818P that is currently on Marsmallow?
thanks
BoyBawang2 said:
hi,
Can I Root & Flash that Nougat ROM on my G4 H818P that is currently on Marsmallow?
thanks
Click to expand...
Click to collapse
NO. you lost signal.
If you try to Flash kdz file but it stops at 9% with error 0x2000 flashing fail .
Try replacing your LGUP dll with this one: LGUP_8994.dll
https://mega.nz/#!b51GGDLL!n42yqpAIaEbgbx8WkoB8DtDAERx3N8tsHhPkC_XDs5M
It's located in this directory:
C:\Program Files (x86)\LG Electronics\LGUP\model\8994
Or this one if you have a 32-bit windows pc:
C:\Program Files\LG Electronics\LGUP\model\8994
And then flash KDZ again
hochocnua said:
NO. you lost signal.
Click to expand...
Click to collapse
Thanks. Can I atleast succeed just on the Rooting part?
BoyBawang2 said:
Thanks. Can I atleast succeed just on the Rooting part?
Click to expand...
Click to collapse
No Root For Marshmallow and Nougat
Sent from my LG-H818 using Tapatalk
Hi, if i flash Nougat this way will I lost network (and dual sim)?
alitavas said:
No Root For Marshmallow and Nougat
Click to expand...
Click to collapse
Thanks. The instructions should have indicated that I should be in Lollipop first before going through the steps.
Future, can i flash firmware h818p normally?
BoyBawang2 said:
Thanks. The instructions should have indicated that I should be in Lollipop first before going through the steps.
Click to expand...
Click to collapse
Sorry - but can you read?
If you read the instructions, you can't miss that Part ?
Yupppiiiii....
Sent from my LG-H870DS using XDA-Developers Legacy app
Please help me...
I successfuly installed nougat on my H818P, but when downgrading i am stuck in download mode, on kdz flashing it always stuck at 25%. In download mode it says modified in red color.
phone is identified as H81529a
esco_448 said:
Please help me...
I successfuly installed nougat on my H818P, but when downgrading i am stuck in download mode, on kdz flashing it always stuck at 25%. In download mode it says modified in red color.
phone is identified as H81529a
Click to expand...
Click to collapse
You must downgrade with kdz file of H815 MM and flash moderm after that.
You must downgrade with kdz file of H815 MM and flash moderm after that.
Click to expand...
Click to collapse
I tried that, It's always showing invalid kdz.
esco_448 said:
I tried that, It's always showing invalid kdz.
Click to expand...
Click to collapse
you need a kdz v20p/MM for H815 and extract dll from it, then replace the old dll from your LGUP dir & and flash your kdz MM for H818.
thank you for the guide
I am using (h815 singapore locked) but I am at europe
1.flashed (H81510C_00_2.kdz -android 5.1) with Lgup
2.flashed rooted (system.rooted.H81510c-EU.img)
3.repated ur guide for nougat
and all works fine for me
thanks
the_naxhoo said:
you need a kdz v20p/MM for H815 and extract dll from it, then replace the old dll from your LGUP dir & and flash your kdz MM for H818.
Click to expand...
Click to collapse
Thanks for your help.
But now it's stucking at 11% (PrimaryGPT step). I am geting this: error message:
Error: Error Code = 0x2000,
Invalid command response
esco_448 said:
Thanks for your help.
But now it's stucking at 11% (PrimaryGPT step). I am geting this: error message:
Error: Error Code = 0x2000,
Invalid command response
Click to expand...
Click to collapse
hm ok, try to extract the dll from your kdz MM H818 and replace the dll again.
Thanks to all, I just restored my device.
I modified H81520p_00_0314.kdz with winhex and replaced H815 with H818P. Used LGUP for flashing.
Can I still use dual sim after 7.0 by h815
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.
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