[GUIDE] How to unbrick RN8 (won't boot only backlight turns on for a second) using EDL

Search This thread
By:
Advanced…
D

donkalli666

Senior Member
Mar 5, 2015
98
50
donkalli666 said:
Ok, I'll try and switch to Arrow or PixelOS without flashing FW. If doing so I mustn't wipe vendor, right?
Click to expand...
Click to collapse
Hi again - Update from my side: As long as I don't flash firmware, everything is good. TWRP is working, Arrow OS and Pixel OS with Magisk also. But I think because of updating MIUI to the latest version before, I'm on the ltest firmware.
 
firefoxos

firefoxos

Senior Member
Jul 9, 2012
121
6
Geryy_the_kid said:
Glad to hear that. If you are new, you will make mistakes, some cases are different. You just need to experiment and experience it yourself.
Click to expand...
Click to collapse

So the only difference in the procedure in the OP to make it work with 8T (willow) is to use a ROM fastboot file for willow?

Nex31313 said:
Hello, version 10.3.1.0 is not working, the phone is still showing the same symptoms. And yes, I did patch the FireHorse file with and without the "Ginkgo_willow_noauth_ddr". No errors occurred during flashing. P.S. Im new to this, tell me if I am missing anything.

EDIT: I managed to get it to work. I used MiUi willow_eea_global_images_V11.0.11.0.PCXEUXM_20200819.0000.00_9.0_eea_23523ab51f\willow_eea_global_images_V11.0.11.0.PCXEUXM_20200819.0000.00_9.0, With the willow_noauth_ddr, It is now in fastboot.
Click to expand...
Click to collapse
Is this the right one, type: Fastboot?

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com xiaomifirmwareupdater.com
the direct link leads to this file

I'm in the process of installing a virgin Windows 10 on a separate drive. I hope the battery is still alive as I think the phone will not charge the battery in that constant quick loop scenario :?

mara91 said:
QPST v2.7.480
Click to expand...
Click to collapse
This version specifically? The latest one is v2.7.496
 
Last edited:
G

Geryy_the_kid

Member
Dec 14, 2022
17
8
firefoxos said:
So the only difference in the procedure in the OP to make it work with 8T (willow) is to use a ROM fastboot file for willow?



Is this the right one, type: Fastboot?

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com xiaomifirmwareupdater.com
the direct link leads to this file

I'm in the process of installing a virgin Windows 10 on a separate drive. I hope the battery is still alive as I think the phone will not charge the battery in that constant quick loop scenario :?


This version specifically? The latest one is v2.7.496
Click to expand...
Click to collapse
Yes and no. Difference is i needed different versions of everything(rom, the patch file and firmware too).
 
tonystark006

tonystark006

Member
Jun 27, 2023
8
0
2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Fail:process fail
2023-06-27 14:29:21.806 Finish Download


anyone know how to fix this issue ? my device is ginkgo . device were originally china rom then switch into eu rom miui12
 
ImmortalChanger

ImmortalChanger

Member
May 14, 2021
14
4
your house
I tried this method with my Redmi Note 8T presenting the same issues, with the same FireHose file you provided and the V11.0.11.0.PCXEUXM Fastboot ROM and it worked perfectly. As I'm writing this, my Note 8T is booting into MIUI and yeah, you literally saved my butt. I decided to write this comment to further confirm that this method does work with willow as well. It has probably something to do with the FireHose file which is specific to the CPU and not the phone as a whole.
 
  • Like
Reactions: dxD7
tonystark006

tonystark006

Member
Jun 27, 2023
8
0
tonystark006 said:
2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Fail:process fail
2023-06-27 14:29:21.806 Finish Download


anyone know how to fix this issue ? my device is ginkgo . device were originally china rom then switch into eu rom miui12
Click to expand...
Click to collapse
anyone can who can help please ?
 
letmecook

letmecook

New member
Sep 14, 2023
1
1
mara91 said:
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8
original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/
many thanks to dxD7 who provided valuable info on how this worked for him


WARNING: this process requires you to enter EDL mode which means you have to separate backplate and short 2 pins on motherboard so USE AT YOUR OWN RISK! since its not quick&easy solution yet.. thanks Xiaomi! (n)

Symptoms:
  • while pressing power button , the display backlight will turn on for approx a second and phone will vibrate and then turn off
  • while pressing power+volume- button, the phone will do the same as above but will show fastboot image for a second too
  • while phone is connected via cable its backlight will turn on for a second and thend turn off repeatedly..
tested on ginko, batch 2020.11 - but should work on other (older phones as well) not tested on 8T-willow but might work - some mention about it is in original thread
note that there is different kind of brick where after turning on the phone only the LED light blinks - it wasn't tested on that situtation but you can try it and pls let me know.



What you will need
clean windows without any previous ROM-flashing or android development drivers is recommended as it looks like windows is unable to fully uninstall previous drivers - they will reappear once device is connected


STEPS:
  1. unpack ROM (for example to Desktop)
  2. unpack prog_emmc_firehose_Sm6125_ddr.zip and place prog_emmc_firehose_Sm6125_ddr.elf from .zip into your unpacked ROM folder: /ginkgo_global_images_V11.0.11.0.PCOMIXM_20201001.0000.00_9.0_global/images/prog_emmc_firehose_Sm6125_ddr.elf (overwrite the old one)
  3. run QFIL.exe and set it up similiarly like in this video (i know it's for 8T and but same principle is applicable here)
  4. leave QFIL.exe running, you will need it later
  5. now the tricky part. remove backlplate, connect phone using USB cable (prefferably stock cable that came with the phone and into USB2 slot) and short these 2 pins to get into EDL mode View attachment 5209521
  6. you should hear windows sound of device plugged in. check in the device manager - it should report as unknown device QUSB_BULK_CID:XXXX_SN:XXXXXXXX
  7. now run xiaomi flash tool 20200314 and it will prompt to install drivers so click Install and check if your unknown device now reports as QUALCOMM HS-USB QDLoader 9008 (if install process happended too fast and you cannot see the driver (this happened to me) please remove anything from MiFlash20200314\log folder and try again)
  8. once the driver is installed, QFIL should show QUALCOMM HS-USB QDLoader 9008 instead of No Port Available
  9. click on Download Content to flash firmware
  10. now my 1st flash failed - I got Sahara Error, so I disconnected the cable, pressed all 3 buttons on phone for ~10seconds until screen blinked and phone vibrated
  11. I connected cable again, shorted these 2 pins to get into EDL mode, pressed Download content again and now it worked (took few minutes) and Download Succeed
  12. hold all 3 buttons for ~10seconds and phone should start up

to my knowledge the error you will get the most in QFIL is Sahara Fail. according to the internet, this might be due to many reasons (bad cable, bad usb port, antivirus running, wrong firmware or firehose or wrong driver but in my case it was the wrong driver - internet is full of various qualcomm driver but I had succes only with the one included in xiaomi flash tool 20200314 ) for more troubleshooting please use for example https://www.nirsoft.net/utils/usbdeview.zip check if your driver's version is same as on the attached image (2.1.0.5)
View attachment 5209555

No reboot nor enabling unsigned drivers, running QFIL as administrator, disabling antivirus was needed in my case.

Maybe some of these steps are unnecesarry, maybe this guide can be written more understandably - sorry for that - i wrote is asap so I won't forget anything I did during process. Please feel free to modify it or I will try to improve it in the future if I brick my phone again and have more knowledge about it..

and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..

EDIT: bricked my phone 3 more times aftrer trying to install RR but was able to recover from all of them again

UPDATE:
user Elinx stated that this happens only with 11-2020 batch and flashing FW 12.01 with recovery. So let's hope it won't happen on other batches..
It is also mentioned here (hope it helps):
see in this topic
and here too
Click to expand...
Click to collapse
Bro, this guide is the one. unbricked my phone in a really short amount of time. TY <3
 
  • Like
Reactions: dxD7
You must log in or register to reply here.

Similar threads

T
[GUIDE] All about unlocking bootloader, TWRP and rooting Redmi Note 8/8T
Replies
451
Views
153K
N
nulnil
F
Guide: MIUI Stock Dialer And SMS app for Global RN8/ RN8 pro
Replies
74
Views
33K
R
ronny08
Y
[Guide] About repairing/fixing the persist partition
Replies
83
Views
42K
S
snows2k
T
[Guide] Flash MIUI OTA/Stock/Any MIUI based ROM from recovery without bricking device
Replies
94
Views
35K
nullifiEdNTITY
nullifiEdNTITY
romulocarlos
[GUIDE] Apps safe to remove
Replies
7
Views
14K
S
sabei

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    letmecook
    letmecook
    mara91 said:
    Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8
    original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/
    many thanks to dxD7 who provided valuable info on how this worked for him


    WARNING: this process requires you to enter EDL mode which means you have to separate backplate and short 2 pins on motherboard so USE AT YOUR OWN RISK! since its not quick&easy solution yet.. thanks Xiaomi! (n)

    Symptoms:
    • while pressing power button , the display backlight will turn on for approx a second and phone will vibrate and then turn off
    • while pressing power+volume- button, the phone will do the same as above but will show fastboot image for a second too
    • while phone is connected via cable its backlight will turn on for a second and thend turn off repeatedly..
    tested on ginko, batch 2020.11 - but should work on other (older phones as well) not tested on 8T-willow but might work - some mention about it is in original thread
    note that there is different kind of brick where after turning on the phone only the LED light blinks - it wasn't tested on that situtation but you can try it and pls let me know.



    What you will need
    clean windows without any previous ROM-flashing or android development drivers is recommended as it looks like windows is unable to fully uninstall previous drivers - they will reappear once device is connected


    STEPS:
    1. unpack ROM (for example to Desktop)
    2. unpack prog_emmc_firehose_Sm6125_ddr.zip and place prog_emmc_firehose_Sm6125_ddr.elf from .zip into your unpacked ROM folder: /ginkgo_global_images_V11.0.11.0.PCOMIXM_20201001.0000.00_9.0_global/images/prog_emmc_firehose_Sm6125_ddr.elf (overwrite the old one)
    3. run QFIL.exe and set it up similiarly like in this video (i know it's for 8T and but same principle is applicable here)
    4. leave QFIL.exe running, you will need it later
    5. now the tricky part. remove backlplate, connect phone using USB cable (prefferably stock cable that came with the phone and into USB2 slot) and short these 2 pins to get into EDL mode View attachment 5209521
    6. you should hear windows sound of device plugged in. check in the device manager - it should report as unknown device QUSB_BULK_CID:XXXX_SN:XXXXXXXX
    7. now run xiaomi flash tool 20200314 and it will prompt to install drivers so click Install and check if your unknown device now reports as QUALCOMM HS-USB QDLoader 9008 (if install process happended too fast and you cannot see the driver (this happened to me) please remove anything from MiFlash20200314\log folder and try again)
    8. once the driver is installed, QFIL should show QUALCOMM HS-USB QDLoader 9008 instead of No Port Available
    9. click on Download Content to flash firmware
    10. now my 1st flash failed - I got Sahara Error, so I disconnected the cable, pressed all 3 buttons on phone for ~10seconds until screen blinked and phone vibrated
    11. I connected cable again, shorted these 2 pins to get into EDL mode, pressed Download content again and now it worked (took few minutes) and Download Succeed
    12. hold all 3 buttons for ~10seconds and phone should start up

    to my knowledge the error you will get the most in QFIL is Sahara Fail. according to the internet, this might be due to many reasons (bad cable, bad usb port, antivirus running, wrong firmware or firehose or wrong driver but in my case it was the wrong driver - internet is full of various qualcomm driver but I had succes only with the one included in xiaomi flash tool 20200314 ) for more troubleshooting please use for example https://www.nirsoft.net/utils/usbdeview.zip check if your driver's version is same as on the attached image (2.1.0.5)
    View attachment 5209555

    No reboot nor enabling unsigned drivers, running QFIL as administrator, disabling antivirus was needed in my case.

    Maybe some of these steps are unnecesarry, maybe this guide can be written more understandably - sorry for that - i wrote is asap so I won't forget anything I did during process. Please feel free to modify it or I will try to improve it in the future if I brick my phone again and have more knowledge about it..

    and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..

    EDIT: bricked my phone 3 more times aftrer trying to install RR but was able to recover from all of them again

    UPDATE:
    user Elinx stated that this happens only with 11-2020 batch and flashing FW 12.01 with recovery. So let's hope it won't happen on other batches..
    It is also mentioned here (hope it helps):
    see in this topic
    and here too
    Click to expand...
    Click to collapse
    Bro, this guide is the one. unbricked my phone in a really short amount of time. TY <3
    View
  • 28
    M
    mara91
    Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8
    original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/
    many thanks to dxD7 who provided valuable info on how this worked for him


    WARNING: this process requires you to enter EDL mode which means you have to separate backplate and short 2 pins on motherboard so USE AT YOUR OWN RISK! since its not quick&easy solution yet.. thanks Xiaomi! (n)

    Symptoms:
    • while pressing power button , the display backlight will turn on for approx a second and phone will vibrate and then turn off
    • while pressing power+volume- button, the phone will do the same as above but will show fastboot image for a second too
    • while phone is connected via cable its backlight will turn on for a second and thend turn off repeatedly..
    tested on ginko, batch 2020.11 - but should work on other (older phones as well) not tested on 8T-willow but might work - some mention about it is in original thread
    note that there is different kind of brick where after turning on the phone only the LED light blinks - it wasn't tested on that situtation but you can try it and pls let me know.



    What you will need
    clean windows without any previous ROM-flashing or android development drivers is recommended as it looks like windows is unable to fully uninstall previous drivers - they will reappear once device is connected


    STEPS:
    1. unpack ROM (for example to Desktop)
    2. unpack prog_emmc_firehose_Sm6125_ddr.zip and place prog_emmc_firehose_Sm6125_ddr.elf from .zip into your unpacked ROM folder: /ginkgo_global_images_V11.0.11.0.PCOMIXM_20201001.0000.00_9.0_global/images/prog_emmc_firehose_Sm6125_ddr.elf (overwrite the old one)
    3. run QFIL.exe and set it up similiarly like in this video (i know it's for 8T and but same principle is applicable here)
    4. leave QFIL.exe running, you will need it later
    5. now the tricky part. remove backlplate, connect phone using USB cable (prefferably stock cable that came with the phone and into USB2 slot) and short these 2 pins to get into EDL mode Screenshot_2.jpg
    6. you should hear windows sound of device plugged in. check in the device manager - it should report as unknown device QUSB_BULK_CID:XXXX_SN:XXXXXXXX
    7. now run xiaomi flash tool 20200314 and it will prompt to install drivers so click Install and check if your unknown device now reports as QUALCOMM HS-USB QDLoader 9008 (if install process happended too fast and you cannot see the driver (this happened to me) please remove anything from MiFlash20200314\log folder and try again)
    8. once the driver is installed, QFIL should show QUALCOMM HS-USB QDLoader 9008 instead of No Port Available
    9. click on Download Content to flash firmware
    10. now my 1st flash failed - I got Sahara Error, so I disconnected the cable, pressed all 3 buttons on phone for ~10seconds until screen blinked and phone vibrated
    11. I connected cable again, shorted these 2 pins to get into EDL mode, pressed Download content again and now it worked (took few minutes) and Download Succeed
    12. hold all 3 buttons for ~10seconds and phone should start up

    to my knowledge the error you will get the most in QFIL is Sahara Fail. according to the internet, this might be due to many reasons (bad cable, bad usb port, antivirus running, wrong firmware or firehose or wrong driver but in my case it was the wrong driver - internet is full of various qualcomm driver but I had succes only with the one included in xiaomi flash tool 20200314 ) for more troubleshooting please use for example https://www.nirsoft.net/utils/usbdeview.zip check if your driver's version is same as on the attached image (2.1.0.5)
    driver.jpg

    No reboot nor enabling unsigned drivers, running QFIL as administrator, disabling antivirus was needed in my case.

    Maybe some of these steps are unnecesarry, maybe this guide can be written more understandably - sorry for that - i wrote is asap so I won't forget anything I did during process. Please feel free to modify it or I will try to improve it in the future if I brick my phone again and have more knowledge about it..

    and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..

    EDIT: bricked my phone 3 more times aftrer trying to install RR but was able to recover from all of them again

    UPDATE:
    user Elinx stated that this happens only with 11-2020 batch and flashing FW 12.01 with recovery. So let's hope it won't happen on other batches..
    It is also mentioned here (hope it helps):
    see in this topic
    and here too
    View
    2
    P
    pswnio
    I have a Redmi Note 8T (willow) and after flashing the wrong firmware i got the same symptoms. At first i tried OP's method but it was failing to start the flashing process because i was trying to use a recent MUI fastboot image for Redmi Note 8T.
    Then I downloaded an older version (willow_global_images_V10.3.1.0.PCXMIXM_20191106.0000.00_9.0_global_b4229c28fb) and the flash process completed successfully!
    I think someone should edit the first post with the above info to make it easier for 8T users, because it only mentions the ROM for Redmi Note 8 (ginko) users.
    Thank you for you guide @mara91
    View
    2
    M
    mara91
    thanks either that or I'm thinking about B7000 glue which looks like many people are using for sticking battery cover
    View
    2
    G
    Geryy_the_kid
    siavash_id said:
    Oh God! that's exactly my problem!! the Symptoms are the same unless I flashed wrong firmware , my phone is redmi note 8 (ginkgo) and somehow I flashed willow firmware successfully and u know the rest... I'm here to ask before I do your steps: is it the same solution for me? as I said all signs are the same, not entering safe mode or recovery , just vibrate and a blink backlight for a sec and goes off again. Do I need to flash ginkgo firmware as an extra step since I flashed wrong firmware? I wait for your answer and doing nothing till u tell me, thanks a lot , u look like an angel for me in this situation.
    oh , by the way , my batch number is 2020,03 on the box.
    Click to expand...
    Click to collapse
    Symptoms are the same, so yeah. Follow my guide, as i wrote it. I suggest to start with the (12.0.1.0) firmware and miui((V12.0.1.0 global). After that go with latest firmware and the rom you need.
    View
    2
    G
    Geryy_the_kid
    Yo. I bricked my phone(redmi note 8t) but i was able to revive it. The screen was flasing when i tried to boot up.

    IMPORTANT NOTES: Not the led notification one problem. On the box it said 03.2020. I guess that is the batch number i have read about.
    Board id: 18.39.0

    Here's what i did:
    Installed adb, fastboot& drivers(needed to manually browse for it). Opened up the phone: tried to boot it, screen was flashing, plugged into pc, shorted the 2 pins. I used QFIL and flashed stock miui((V12.0.1.0 global) with the corresponding firmware(12.0.1.0) and a file(you need to copy this file to the roms' "images" folder) i found in another thread. Successfully booted into the stock rom. After that i fastbooted, flashed vbmeta and twrp 3.7.0_12-1-gingko via cmd.
    Successfully booted into twrp, wipe--->format data, typed "yes". Next step was advanced wipe: Dalvik/art cache, cache, vendor, system, data és internal storage. Afterwards installed the newest firmware(V12.5.6.0.RCXMIXM at the time of writing this). Tested: Arrow, CrDroid, Lineage, Ricedroid. All of them were android 13 and the latest ones and all of them worked flawlessly.

    Edit: added some stuff

    qfil settings.png
    View

New posts