Moto G4 Plus hard brick!!! - Moto G4 Plus Questions & Answers

Hello, I bricked my moto g4 plus a while ago and it does not go into fastboot and does not connect, so there is no way to install a new ROM, the only thing it does is flash the led, when I connect it on the computer it recognizes it as Qualcomm Hs-usb qdloader 9008, I saw in some places I need a blankflash for the bike g4 plus xt 1640, I tried one but it did not work. I wanted to know if anyone knows how to solve or I would have a different blankflash. Sorry for my English, I'm not American.

How did you brick your device (was it with a firmware downgrade)?

echo92 said:
How did you brick your device (was it with a firmware downgrade)?
Click to expand...
Click to collapse
No, I just decided to remove root by installing rom 6.0.1, after an update via OTA the screen went dark and it bricked.

echo92 said:
How did you brick your device (was it with a firmware downgrade)?
Click to expand...
Click to collapse
I think I just need a blank flash that works, if you know of any for the g4 plus bike I appreciate it.

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Try this
---------- Post added at 03:34 PM ---------- Previous post was at 03:34 PM ----------
Do you have TWRP installed ?

zap456 said:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Try this
---------- Post added at 03:34 PM ---------- Previous post was at 03:34 PM ----------
Do you have TWRP installed ?
Click to expand...
Click to collapse
Well, I even had it bricked, as I said before it does not give a sign of life does not go into fastboot, or TWRP, I do not know what else to do.

zap456 said:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Try this
---------- Post added at 03:34 PM ---------- Previous post was at 03:34 PM ----------
Do you have TWRP installed ?
Click to expand...
Click to collapse
I had tried this method but received the following error:
C: \ Users \ Bruno \ Downloads \ blank-flash \ blankflash>. \ Qboot.exe blank-flash
Motorola qboot utility version 3.40
[0.000] Opening device: \\. \ COM4
[0.003] Detecting device
[0.003] ReadFile () failed, GetLastError () = 0
[0.506] ReadFile () failed, GetLastError () = 0
[1.010] ReadFile () failed, GetLastError () = 0
[1.011] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[1.011] Check qboot_log.txt for more details
[1,012] Total time: 1013s
FAILED: qb_flash_singleimage () -> sahara_greet_device () -> change_mode () -> do_hello ()
-> IO error
C: \ Users \ Bruno \ Downloads \ blank-flash \ blankflash> pause

Software00 said:
I had tried this method but received the following error:
C: \ Users \ Bruno \ Downloads \ blank-flash \ blankflash>. \ Qboot.exe blank-flash
Motorola qboot utility version 3.40
[0.000] Opening device: \\. \ COM4
[0.003] Detecting device
[0.003] ReadFile () failed, GetLastError () = 0
[0.506] ReadFile () failed, GetLastError () = 0
[1.010] ReadFile () failed, GetLastError () = 0
[1.011] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[1.011] Check qboot_log.txt for more details
[1,012] Total time: 1013s
FAILED: qb_flash_singleimage () -> sahara_greet_device () -> change_mode () -> do_hello ()
-> IO error
C: \ Users \ Bruno \ Downloads \ blank-flash \ blankflash> pause
Click to expand...
Click to collapse
Did you try the tips listed in the opening post linked by zap456? There's a section about the same error you're experiencing, where it may take several tries for Qboot to connect to your device.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Click to expand...
Click to collapse

echo92 said:
Did you try the tips listed in the opening post linked by zap456? There's a section about the same error you're experiencing, where it may take several tries for Qboot to connect to your device.
Click to expand...
Click to collapse
Yes, I tried several times.

Download the stock firmware from : https://www.androidfilehost.com/?fid=889764386195918175
And flash it using qpst or qfil and that should fix each and every problem on your phone ,
Hit the thanks button and ask if you have any questions.

zap456 said:
Download the stock firmware from : https://www.androidfilehost.com/?fid=889764386195918175
And flash it using qpst or qfil and that should fix each and every problem on your phone ,
Hit the thanks button and ask if you have any questions.
Click to expand...
Click to collapse
Would there be any tutorial how to do this?
Well, I've never really looked at this part, it's the first time a cell phone has stopped working.

zap456 said:
Download the stock firmware from : https://www.androidfilehost.com/?fid=889764386195918175
And flash it using qpst or qfil and that should fix each and every problem on your phone ,
Hit the thanks button and ask if you have any questions.
Click to expand...
Click to collapse
Would there be any tutorial how to do this?
Well, I've never really looked at this part, it's the first time a cell phone has stopped working.

zap456 said:
Download the stock firmware from : https://www.androidfilehost.com/?fid=889764386195918175
And flash it using qpst or qfil and that should fix each and every problem on your phone ,
Hit the thanks button and ask if you have any questions.
Click to expand...
Click to collapse
Ok, I've already found a tutorial, I'll try anything I notice, thanks for the help.

zap456 said:
Download the stock firmware from : https://www.androidfilehost.com/?fid=889764386195918175
And flash it using qpst or qfil and that should fix each and every problem on your phone ,
Hit the thanks button and ask if you have any questions.
Click to expand...
Click to collapse
I can not find something compatible with Qfil in the ROM folder that you passed me, I click Search, I click on the ROM folder and there is no file.

Software00 said:
I can not find something compatible with Qfil in the ROM folder that you passed me, I click Search, I click on the ROM folder and there is no file.
Click to expand...
Click to collapse
Wait let me check , do you mean that you can't find the .xml file ??

zap456 said:
Wait let me check , do you mean that you can't find the .xml file ??
Click to expand...
Click to collapse
yes bro, we are not able to detect the firehose programmer file ,the rawprogram file and the patch file in the stock firmware.

There is a firmware : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view
Check its contents before downloading it .
After downloading it you would require this to unzip the folder :http://www.7-zip.org/download.html I think winrar shows some error in extracting the files.

zap456 said:
There is a firmware : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view
Check its contents before downloading it .
After downloading it you would require this to unzip the folder :http://www.7-zip.org/download.html I think winrar shows some error in extracting the files.
Click to expand...
Click to collapse
That looks to be the same stock ROM as the NPJ25.93-14 ROM linked here? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
If so, I don't think it includes the required files for QFIL to successfully recover a bricked device (namely those named by Aditya_kumar), particularly if the bootloader is corrupted. You'll need a programmer.mbn for MSM8952 (our device's Snapdragon 617), probably also signed by Motorola and the various .xml files to tell QFIL what to flash. Also, programmers appear to be checking the bootloader whether they can permit a flash to occur, so we'd need a recent programmer.
I wish it were as simple as downloading QFIL and flashing a stock ROM to rescue a bricked device...

echo92 said:
That looks to be the same stock ROM as the NPJ25.93-14 ROM linked here? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
If so, I don't think it includes the required files for QFIL to successfully recover a bricked device (namely those named by Aditya_kumar), particularly if the bootloader is corrupted. You'll need a programmer.mbn for MSM8952 (our device's Snapdragon 617), probably also signed by Motorola and the various .xml files to tell QFIL what to flash. Also, programmers appear to be checking the bootloader whether they can permit a flash to occur, so we'd need a recent programmer.
I wish it were as simple as downloading QFIL and flashing a stock ROM to rescue a bricked device...
Click to expand...
Click to collapse
BRO, I think servicefile and flashfile(both are xml files containing info. on what to flash) included in the stock can work as rawprogram file and patch file. But the point comes as we need firehose programmer file( mbn file) too. I don't think that fsg.mbn file( only mbn fie in stock rom ) can compesate for the firehose programmer file.

I am already getting desperate, I do not know there for you but I live in Brazil the Moto G4 Plus here is 1,500 R $ when I bought it, throw it away so because of a hardbrick is very desperate, no one could solve?

Related

LGUP for most International, and Domestic G5s

I have done my best to make sure most of the LG G5s out there will work with LGUP.
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
now for the fun bit:
1. Download and extract the LGUP.zip file from here as it contains everything you'll need except the firmwares.
2. To install the drivers for the device, go to the Drivers folder located in LGUP, and select InstallUSB.exe for a 32-bit system, or InstallUSB64.exe for a 64-bit system.
3. Install LGUP_Lab_Frame_Ver_1_11 that is in the LGUP folder
4. Install either the G5x86.reg or the G5x64.reg depending on whether you have a 32 or 64 bit windows installed.
5. Put the "model" folder in the LG Electronics\LGUP folder which will be either in C:\Program Files or C:\Program Files (x86) depending on whether you have a 32 or 64 bit windows installed
6. Put phone in download mode ( Phone off, vol up while plugging in usb from PC), start LGUP
7. Make sure you see a com # and phone model and at the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the .tot or .kdz file listed for your device, then hit start and wait for the magic.
Devices supported:
A992
F700K
F700L
F700S
H820
H830
H831
H850
H850TR
H858
H860
H860N
H868
LS992
RS988
US992
VS987
If I have not listed your device, list the exact model name (i.e LGLS992) in the comments below and I will add it for download.
I give creds to autoprime for his good work. If I missed anyone, I am giving you credits and apologizing now for not mentioning you.
Sorry for a questions that may be dumb, but what is this Tool supposed to do?
Sent from my LG-H850 using Tapatalk
Just a program that lets you flash firmware files to the described phone models
gwolfu said:
Just a program that lets you flash firmware files to the described phone models
Click to expand...
Click to collapse
Any possibility of achieving root with this on locked bootloaders?
Sent from my SM-N900T using Tapatalk
ForgottenSolstace said:
Any possibility of achieving root with this on locked bootloaders?
Click to expand...
Click to collapse
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Veliion said:
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Click to expand...
Click to collapse
This only if the model support the fastboot oem unlock command.
Without an unlocked bootloader is not possible to obtain root on Marshmallow, the only way would be find an exploit.
Sent from my LG G5 using XDA Labs
A992 in OP is typo.. should be AS992 obviously.
New model you could add:
H820PR
H850K
Thank you!
can i install gapps using this tool? i have a H868 chinese version, google services are not preinstalled .
Broken Link =(
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
AmorImpermissus said:
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
Click to expand...
Click to collapse
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
gwolfu said:
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
Click to expand...
Click to collapse
Thanks a bunch gwolfu. However, what I really need are the LG<model>_DLL.msi files. Specifically, I need it for the RS988. It was listed in the supported devices at the beginning, but can't find it =(
LGUP not working...
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
milennium said:
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
Click to expand...
Click to collapse
When you open "Settings" -> "General" tab -> "About phone" -> "Hardware info" what does it have for "Model number?"
Model number: LG-H850
OK looking at the screenshot, I'm wondering if somehow the install got messed up. If you go to:
c:\program files (x86)\LG Electronics\LGUP\Model
What are the contents?
Also, open powershell as an administrator (usually can just type "powershell" from an elevated command prompt) and run this command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
Then copy/paste the results so I can see them =)
In regedit, go to:
HKCU:\software\LG Electronics\LGUP\Model
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
milennium said:
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
Click to expand...
Click to collapse
You should be able to use the LGUP tool regardless of whether or not you have an unlocked bootloader. You may not be able to flash every kind of *.tot file, but whether or not your phone's bootloader is unlocked will have nothing to do with that error you're getting.
What about the output of the powershell command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
?
Here is the result Powershell command:
milennium said:
Here is the result Powershell command:
Click to expand...
Click to collapse
OK, so, do the following, and then try to run LGUP with the phone connected, and let's see if it works:
1. Create a blank notepad file
2. Save it as something like h850.reg to your desktop where you can find it easily.
3. With the file still open in notepad, copy/paste the info below info and then save it again.
4. Close the file, then double-click it from your desktop to import it.
I've also attached it as a *.txt file which you can just change the extension to *.reg if that's easier:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\H850]
"MODEL_NAME"="H850"
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H830.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
"MODEL_NAME"="LGH850"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2]
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\H850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"

Update LG G4 H818P to android 7 by LG-H815 Official v29A.

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

[GUIDE] Proper H815 unbrick through QFIL (Files included)

WARNING - This guide is only for H815 International G4 variant (official unlock available)
Much thanks to steadfasterX for the files and helping me to unbrick my device this way.
This guide is for devices in Qualcomm 9008 mode (hard brick)
1. Download this archive.
2. Install every driver/runtime and QPST from the "software_drivers" folder (do not install virtualhere_client files, those are not needed for unbricking)
3. Extract "flashing" folder.
3. If your device is not in 9008 mode already, force boot to it (tutorial in "stuff" folder in archive, or look up LG G4 EMMC shorting)
It should show up something like this when properly in 9008 mode (QHUSB_BULK in device manager means drivers are not properly installed, try again)
4. Once your device is in 9008 mode, Open QFIL, disconnect it from the computer, remove the battery and connect it back to the computer with battery removed.
5. Proceed to select the files from the "flashing" folder you extracted in QFIL, then press the "Download" button.
If all goes right, it should flash properly and your device should be able to enter download mode, then flash stock .kdz with LGUP or any other software like usual.
According to steadfasterX, this could work on other H815 variants, but DO NOT proceed if you are afraid of bricking the device completely.
For further support join #Carbon-user IRC channel on freenode [URL="https://webchat.freenode.net/?channels=Carbon-user](direct link)[/URL]
yes.
the above has been proven on several devices for ppl contacting me!
Thanks for taken the time to write down the guide
In general that may work on any H815 device but no guarantees. Most important regarding this is: ARB again. If you have ARB > 0 this will brick your device
After you have done the above you will be able to get into the Download mode again to flash whatever you like to restore.
Cheers and have fun
sfX
UPDATE: for UsU devices
UsU devices have to replace files from the UsU unlock zip:
aboot_UsU.img (UsU unlock zip) --> flashing/emmc_appsboot.mbn
laf_UsU.img (UsU unlock zip) --> flashing/laf.img
rawres_UsU.img (UsU unlock zip) --> flashing/raw_resources.img
UPDATE: added mirror link
https://www.androidfilehost.com/?fid=1322778262904000036
UPDATE: 2020-08-20 :
Main Download link from the OP has been moved to:
http://leech.binbash.rocks:8008/unbricking/qfil/h815/
--> G4-h815_fullunbrick_working_7a3ae5809224d.zip
.
steadfasterX said:
yes.
the above has been proven on several devices for ppl contacting me!
Thanks for taken the time to write down the guide
In general that may work on any H815 device but no guarantees. Most important regarding this is: ARB again. If you have ARB > 0 this will brick your device
After you have done the above you will be able to get into the Download mode again to flash whatever you like to restore.
Cheers and have fun
sfX
Click to expand...
Click to collapse
Please help!
Validating Application Configuration
Load APP Configuration
COM:3
SAHARA:True
SAHARA:E:\INSTALL\Mobile\LGg4\MBNS\mi4c\prog_emmc_firehose_8992_ddr.mbn
SEARCHPATH:E:\INSTALL\Mobile\LGg4\MBNS\mi4c
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: E:\INSTALL\Mobile\LGg4\MBNS\mi4c
Programmer Path:E:\INSTALL\Mobile\LGg4\MBNS\mi4c\prog_emmc_firehose_8992_ddr.mbn
Programmer Path:F:\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
Image Search Path: F:\h815_full_working_7a3ae5809224d\flashing
Image Search Path: F:\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: F:\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:F:\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Start Download
Program Path:F:\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:FireHose Fail Failed to send Firehose NOP to the phone.
Finish Download
Thanks in advance.
tithitoy said:
Please help!
Validating Application Configuration
Load APP Configuration
COM:3
SAHARA:True
SAHARA:E:\INSTALL\Mobile\LGg4\MBNS\mi4c\prog_emmc_firehose_8992_ddr.mbn
.......
Click to expand...
Click to collapse
If you do not use my files I can't help.
Sent from my LG-H815 using XDA Labs
I tried to folow this tutorial but I wasnt able to flash my g4 H815 i dont know why. Here are my logs: https://bpaste.net/show/57c550e06998
sr.arenisca said:
I tried to folow this tutorial but I wasnt able to flash my g4 H815 i dont know why. Here are my logs: https://bpaste.net/show/57c550e06998
Click to expand...
Click to collapse
keep in mind that QDL is very sensitive:
1) do not wait longer then a few seconds after you entered the QDL mode to push the files
2) if you have used it once you need to re-do the steps to enter QDL mode before flashing again
.
steadfasterX said:
keep in mind that QDL is very sensitive:
1) do not wait longer then a few seconds after you entered the QDL mode to push the files
2) if you have used it once you need to re-do the steps to enter QDL mode before flashing again
.
Click to expand...
Click to collapse
I did not wait more than 3-4 seconds in the last try and i got the same error : https://bpaste.net/show/012543a80981
Im doing it without batery if it matters.
And im stuck in that mode so i only need to connect the device to the computer to enter that mode.
Should I force the enter in that mode sorting the pins?
Your links are not working for me.
I bricked my phone by accidentally trying to install a corrupted bootloader .zip with TWRP. My phone almost totally stopped working, just giving me a black screen after turning it on, not even fastboot or the download mode worked, and I thought I was totally screwed. This was my last ditch attempt to save my G4 after days of researching and trying things I had totally written off my G4 but then I came across this. So I took apart my G4 and did the test point shorting method along with this guide AND IT WORKED. I was amazed. My phone acted weird for a little while, crashing and rebooting randomly, I think that might have been because I took it apart in an environment that is not EMC protected. But after a while everything returned to normal. Glad I don't have to buy a new phone and I can keep using my G4, which I love compared to anything that is on the market today (**** all those phones with no removable battery and SD).
Anyway thanks a lot to steadfasterX and OP and whoever else was involved in helping to create this method.
not working for me
https://bpaste.net/show/9423b4b8c0a3
ososmam said:
not working for me
https://bpaste.net/show/9423b4b8c0a3
Click to expand...
Click to collapse
Sure. If not following the guide its clear it will not work. You are missing step 2 which also installs qpst and qfil into C:\ (programs.. Qualcomm)
You're using another qfil so it can't work.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Sure. If not following the guide its clear it will not work. You are missing step 2 which also installs qpst and qfil into C:\ (programs.. Qualcomm)
You're using another qfil so it can't work.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
can you provide my with qfil it not provided i installed the qpst but cannont find qfil in the zip file
ososmam said:
can you provide my with qfil it not provided i installed the qpst but cannont find qfil in the zip file
Click to expand...
Click to collapse
Install qpst from that zip. Go into c: programs qualcomm qpst and there you find qfil.exe (I can't write down the exact path as I'm not on my pc atm but you will find it)
Sent from my LG-H815 using XDA Labs
still black screen nothing happened after finished
my device is h815p
https://bpaste.net/show/1ee73cea27f9
ososmam said:
still black screen nothing happened after finished
my device is h815p
https://bpaste.net/show/1ee73cea27f9
Click to expand...
Click to collapse
This looks better now.
What happens in the device manager when you connect the device while the screen is black?
Btw: How did you come to the situation that you need to flash with qfil??
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This looks better now.
What happens in the device manager when you connect the device while the screen is black?
Btw: How did you come to the situation that you need to flash with qfil??
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
nothing detected it just vibrate when press the power button
flashed a worng rom v29 without usu support ended with this situation
steadfasterX said:
This looks better now.
What happens in the device manager when you connect the device while the screen is black?
Btw: How did you come to the situation that you need to flash with qfil??
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
finally it boot again i chanced
these 3 files laf , emmc_appsboot , raw_resources
with laf,aboot, raw_resources from h815-usu unlock files
and edited the raw-program to match these files
also change the recovery with twrp
fianaly can boot to fastboot and twrp
ososmam said:
finally it boot again i chanced
these 3 files laf , emmc_appsboot , raw_resources
with laf,aboot, raw_resources from h815-usu unlock files
and edited the raw-program to match these files
also change the recovery with twrp
fianaly can boot to fastboot and twrp
Click to expand...
Click to collapse
Sure UsU devices don't work with this files. These are for regular h815 devices or locked h815 ones.
the way you have done to make it work is correct for UsU devices.
keep in mind that when requesting help it's important to mention as many details as possible.. UsU is such an important detail..
Have fun
Sent from my LG-H815 using XDA Labs
Hello, bricked my usu h815, flashing aboot file. Trying fix, but have error. Any chances for me
Validating Application Configuration
Load APP Configuration
COM:4
SAHARA:True
SAHARA:C:\Program Files\Qualcomm\QPST\bin\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\Program Files\Qualcomm\QPST\bin
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:True
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:True
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:5
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Program Files\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files\Qualcomm\QPST\bin\rawprogram0.xml
PATCH file path:C:\Program Files\Qualcomm\QPST\bin\patch0.xml
Programmer Path:C:\Program Files\Qualcomm\QPST\bin\prog_emmc_firehose_8992_lite.mbn
Image Search Path: C:\Program Files\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files\Qualcomm\QPST\bin\rawprogram0.xml
PATCH file path:C:\Program Files\Qualcomm\QPST\bin\patch0.xml
FireHose Configuration Cancelled
Start Download
Program Path:C:\Program Files\Qualcomm\QPST\bin\prog_emmc_firehose_8992_lite.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Enable Ack Raw Data Every 100Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:4
Sending NOP
FireHose Log: Binary build date: Mar 3 2015 @ 19:29:19
FireHose Log: fh.attrs.Verbose is set to 0
FireHose Log: Chip serial num: 6178897 (0x5e4851)
FireHose Log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: Host's hash buffer size not provided or 0; using 8192
FireHose Log: fh.attrs.MaxPayloadSizeToTargetInBytes > FIREHOSE_CHANNEL_BUFFER_SIZE
FireHose Log: Calling hotplug_poll_device('MMC')
Invalid response NAK
CONFIGURE: Fail Code 13
Failed to send the Firehose configure packet
Download Fail:FireHose Fail FireHose Fail:Failed to configure the device in Firehose mode
Finish Download
Cisuwek said:
Hello, bricked my usu h815, flashing aboot file. Trying fix, but have error. Any chances for me
Click to expand...
Click to collapse
You are not using the unbrick zip provided in the OP.
I told billion of times that using the wrong files will brick your device in a way which is unrecoverable.
Besides that: UsU devices have to replace files from the UsU unlock zip:
aboot_UsU.img (UsU unlock zip) --> flashing/emmc_appsboot.mbn
laf_UsU.img (UsU unlock zip) --> flashing/laf.img
rawres_UsU.img (UsU unlock zip) --> flashing/raw_resources.img

[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

Categories

Resources