General RedMagic 7&7Pro EDL firehose

Search This thread

JerryYin

Senior Member
Apr 15, 2018
186
169
Shenzhen
This is the firehose for RedMagic 7 and 7Pro, it should work on both CN and global version.

Extracted from the leaked CN firmware.

A small gift for all RedMagic 7&7Pro user.

Good Luck
 

Attachments

  • prog_firehose_ddr.zip
    697.5 KB · Views: 517
I checked, it didn't work for me, on rm 7 PRO.

02:13:54: INFO: User requested *semi-verbose* logging with --loglevel=1 - This is default
02:13:54: INFO: User wants to talk to port '\\.\COM3'
02:13:54: DEBUG: port_fd=0x128

02:13:54: INFO: Took 0.00000000 seconds to open port
02:13:54: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
02:13:54: INFO: If you don't want this, use --dontsorttags

02:13:54: INFO: Sending <configure>
02:13:54: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>

============================================================================================================

02:13:54: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
02:13:54: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
02:13:54: DEBUG: CharsInBuffer = 16
02:13:54: DEBUG: printBuffer:5423 PRETTYPRINT Buffer is 16 bytes

02:13:54: DEBUG: printBuffer:5500 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
02:13:54: DEBUG: printBuffer:5513




_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: DetermineTag:6224 XML not formed correctly. Expected a &lt; character at loc 0


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: GetNextPacket:7298 3. TAG not found or recognized


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: GetNextPacket:7308

There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!

This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target

Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
 

JerryYin

Senior Member
Apr 15, 2018
186
169
Shenzhen
I checked, it didn't work for me, on rm 7 PRO.

02:13:54: INFO: User requested *semi-verbose* logging with --loglevel=1 - This is default
02:13:54: INFO: User wants to talk to port '\\.\COM3'
02:13:54: DEBUG: port_fd=0x128

02:13:54: INFO: Took 0.00000000 seconds to open port
02:13:54: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
02:13:54: INFO: If you don't want this, use --dontsorttags

02:13:54: INFO: Sending <configure>
02:13:54: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>

============================================================================================================

02:13:54: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
02:13:54: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
02:13:54: DEBUG: CharsInBuffer = 16
02:13:54: DEBUG: printBuffer:5423 PRETTYPRINT Buffer is 16 bytes

02:13:54: DEBUG: printBuffer:5500 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
02:13:54: DEBUG: printBuffer:5513




_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: DetermineTag:6224 XML not formed correctly. Expected a &lt; character at loc 0


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: GetNextPacket:7298 3. TAG not found or recognized


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


02:13:54: {ERROR: GetNextPacket:7308

There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!

This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target

Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
File updated, try again
 

JerryYin

Senior Member
Apr 15, 2018
186
169
Shenzhen
I checked, it didn't work for me. rm 7 PRO

23:25:13: INFO: User requested *semi-verbose* logging with --loglevel=1 - This is default
23:25:13: INFO: User wants to talk to port '\\.\COM3'
23:25:13: DEBUG: port_fd=0x12C

23:25:13: INFO: Took 0.00000000 seconds to open port
23:25:13: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
23:25:13: INFO: If you don't want this, use --dontsorttags

23:25:13: INFO: Sending <configure>
23:25:13: DEBUG: CHANNEL DATA (P0000) (H00202) ( 227 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="ufs" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>

============================================================================================================

23:25:13: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
23:25:13: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
23:25:13: DEBUG: CharsInBuffer = 16
23:25:13: DEBUG: printBuffer:5423 PRETTYPRINT Buffer is 16 bytes

23:25:13: DEBUG: printBuffer:5500 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
23:25:13: DEBUG: printBuffer:5513




_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


23:25:13: {ERROR: DetermineTag:6224 XML not formed correctly. Expected a &lt; character at loc 0


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


23:25:13: {ERROR: GetNextPacket:7298 3. TAG not found or recognized


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


23:25:13: {ERROR: GetNextPacket:7308

There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!

This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target

Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Check your phone and your setting on your PC, the file confirmed working
 
If your going to do it do it right! You need the rawprogram0.xml to use QFIL and the patch0.xml is important as well. With all the files you can now very carefully dump and root the complete ROM. Now can I get a little TWRP or OrangeFox Recovery action please?!?


Any code used in the creation of the files below are properties of their respective owners; ZTE, Nubia, Redmagic, Google, Qualcomm, the elf nextdoor, some version of the GPL or otherwise and licensed accordingly.
I make no claim to the code below expressly, implied or otherwise.
 

Attachments

  • FIREHOSE.zip
    681.3 KB · Views: 86
Last edited:

Apostalus

Member
Apr 6, 2023
25
1
Allright, Guys and Gals

Looks like I hard bricked my NX709J and need help... the rawprogram0.html is improperly written, I've noticed, and my QFIL always comes back with errors. What I need is someone to send me a backup file of their NX709Jso I may restore mine out of EDL. Any biters? Please???
 

amar am

Member
Oct 4, 2020
6
0
إذا كنت ستفعل ذلك فافعله بشكل صحيح! أنت بحاجة إلى ملف Rawprogram0.xml لاستخدام QFIL كما أن ملف patch0.xml مهم أيضًا. مع جميع الملفات، يمكنك الآن تفريغ ذاكرة القراءة فقط بالكامل وتجذيرها بعناية شديدة. الآن هل يمكنني الحصول على القليل من إجراءات TWRP أو OrangeFox Recovery من فضلك؟!؟


أي رمز مستخدم في إنشاء الملفات أدناه هو ملك لأصحابها؛ ZTE، Nubia، Redmagic، Google، Qualcomm، the elf nextdoor، بعض إصدارات GPL أو غير ذلك ويتم ترخيصها وفقًا لذلك.
لا أتقدم بأي مطالبة بالرمز أدناه بشكل صريح أو ضمني أو غير ذلك.
7 pro ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    This is the firehose for RedMagic 7 and 7Pro, it should work on both CN and global version.

    Extracted from the leaked CN firmware.

    A small gift for all RedMagic 7&7Pro user.

    Good Luck
    1
    hello , check file format after unzip.... MELF -> ELF ...
    I have a bricked Nubia 7 PRO device. It enters fastboot and EDL mode. What needs to be done to flash the bootloader using the firehose file. I run QFIL, and in addition to .elf I see that I need rawprogram.xml. Where can I get it?