General RMX3363 11 RUI4 F06 A13 Export QPST (Qualcomm Product Support Tools) [EDIT : DELETED]

[enonaw]

DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE

You must have a loader file signed by Realme, not supplied in the archive.

(I recommend that you only use it to resolve a hard brick. In the event of a soft brick (access to the bootloader), there is bound to be a solution using fastboot : see here)

ONLY FOR UNLOCKED BOOTLOADER !

Here (19.2 GB) : (deleted, seems not to be a valid Realme QFIL firmware)

 

[drummer1839]

Hi ! It's a flash tool?

 

[enonaw]

Hi ! It's a flash tool?

It's the RUI4-F06 firmware that you can flash with QPST : Last version

 

[drummer1839]

Ok thanks

 

[s1yn]

I'm getting Sahara and/or FHLoader error almost instantly when i try to Flash, whats wrong?

 

[enonaw]

I'm getting Sahara and/or FHLoader error almost instantly when i try to Flash, whats wrong?

What error ? (I didn't test it)

 

[s1yn]

Always some SaharaServer or FHLoader error cant remember what it says, afk atm...

 

[s1yn]

This is what it says in my log...

 

[enonaw]

DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE

You must have a loader file signed by Realme, not supplied in the archive.

1. Install Qualcomm drivers

- Open the device manager on PC
- Smartphone switched off, hold down the 2 volume buttons and connect it to the PC's USB port (use 2.0 instead of 3.0 if possible) to enter EDL (Emergency DownLoad) mode
- Qualcomm HS-USB QDLoader 9008 should be displayed in the COM ports section
- If an unknown device of type QUSB_BULK is displayed, you need to install the drivers
- Download here

Don't forget that EDL mode lasts 10 seconds when idle, so you need to install the drivers quickly.

2. Install QPST/QFIL

- Download here

3. Flash the firmware

- Run QFIL (Qualcomm Flash Image Loader) as administrator
- Click on Configuration then FireHose Configuration
- Configure as shown in the screenshot below :

- Return to the main menu and select Flat Build in the Select Build Type item
- Click on Browse in the Select Programmer item
- Select the signed .elf loader from Realme (the prog_firehose_ddr.elf and prog_firehose_ddr_fwupdate.elf files in the unzipped firmware folder don't work)
- Click on Load XML and select the 6 rawprograms files, then select the 6 patch files
- Smartphone switched off, hold down the 2 volume buttons and connect it to the PC's USB port (use 2.0 instead of 3.0 if possible) to enter EDL (Emergency DownLoad) mode
- As soon as you hear the connection sound, release the volume buttons and quickly (within 10 seconds) press Select port, select the detected port, press OK and then press the Download button

 

[enonaw]

This is what it says in my log...

If you have access to bootloader, see here

 

[rd.emon]

I am getting this error every time I try QPST/Qfil. I don't have access to Bootloader & Recovery. My phone is bricked and only accessible in EDL via Qualcomm driver. Please help me

 

[enonaw]

I am getting this error every time I try QPST/Qfil. I don't have access to Bootloader & Recovery. My phone is bricked and only accessible in EDL via Qualcomm driver. Please help me

Change the "sparse" parameter from true to false in the "userdata.img" line of the rawprogram0.xml file.

 

[rd.emon]

Changed the rawprogram0.xml, Still getting the Sahara Error

14:19:26: WARNING: find_file:8463 Couldn't find the file 'oplus', returning NULL

14:19:26: {ERROR: handleProgram:9270 'oplus' not found. You could possibly try --notfiles=oplus,OtherFileToSkip.bin (note, exiting since you specified --noprompt)

 

[enonaw]

Changed the rawprogram0.xml, Still getting the Sahara Error

14:19:26: WARNING: find_file:8463 Couldn't find the file 'oplus', returning NULL

14:19:26: {ERROR: handleProgram:9270 'oplus' not found. You could possibly try --notfiles=oplus,OtherFileToSkip.bin (note, exiting since you specified --noprompt)

Did you try the "--notfiles=oplus" ?

 

[rd.emon]

Did you try the "--notfiles=oplus" ?

How to do that? I don't know!

 

[enonaw]

How to do that? I don't know!

You can try to delete the "oplus" line into the rawprogram3.xml file (make a backup of the file before).

 

[rd.emon]

You can try to delete the "oplus" line into the rawprogram3.xml file (make a backup of the file before).

this time
15:03:43: WARNING: find_file:8463 Couldn't find the file 'dynamic_nvbk.bin', returning NULL

15:03:43: {ERROR: handleProgram:9270 'dynamic_nvbk.bin' not found. You could possibly try --notfiles=dynamic_nvbk.bin,OtherFileToSkip.bin (note, exiting since you specified --noprompt)


Is there any other method of unbricking the phone?

 

[enonaw]

this time
15:03:43: WARNING: find_file:8463 Couldn't find the file 'dynamic_nvbk.bin', returning NULL

15:03:43: {ERROR: handleProgram:9270 'dynamic_nvbk.bin' not found. You could possibly try --notfiles=dynamic_nvbk.bin,OtherFileToSkip.bin (note, exiting since you specified --noprompt)


Is there any other method of unbricking the phone?

I understand. Take your old rawprogram3.xml file (with the "oplus" line) and rename the following files in the firmware's IMAGES folder :

- oplusXXXXX.bin > oplus.bin
- dynamic_nvbk.XXXXX.bin > dynamic_nvbk.bin
- static_nvbk.XXXXX.bin > static_nvbk.bin

I don't know of any method other than QFIL for hard unbrick. How did you hard brick your phone ?

 

[rd.emon]

I understand. Take your old rawprogram3.xml file (with the "oplus" line) and rename the following files in the firmware's IMAGES folder :

- oplusXXXXX.bin > oplus.bin
- dynamic_nvbk.XXXXX.bin > dynamic_nvbk.bin
- static_nvbk.XXXXX.bin > static_nvbk.bin

I don't know of any method other than QFIL for hard unbrick. How did you hard brick your phone ?

Thanks a lot for your patience and effort. The previous error is now solved. But it is looking for super.img file


15:34:36: WARNING: find_file:8463 Couldn't find the file 'super.img', returning NULL
15:34:36: DEBUG: ==================================================================================
15:34:36: DEBUG: ==================================================================================
15:34:36: INFO: Looking for file 'userdata.img'
15:34:36: DEBUG: 1. Calling stat('D:\copy_ofp\flash_bin\IMAGES\userdata.img')
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: DEBUG: Trying get filesize, calling fseek()
15:34:36: DEBUG: Found 'D:\copy_ofp\flash_bin\IMAGES\userdata.img' (2920740 bytes)
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...

15:34:36: {ERROR: sparse_open:2625 Unknown chunk type cac2

 

[enonaw]

Thanks a lot for your patience and effort. The previous error is now solved. But it is looking for super.img file


15:34:36: WARNING: find_file:8463 Couldn't find the file 'super.img', returning NULL
15:34:36: DEBUG: ==================================================================================
15:34:36: DEBUG: ==================================================================================
15:34:36: INFO: Looking for file 'userdata.img'
15:34:36: DEBUG: 1. Calling stat('D:\copy_ofp\flash_bin\IMAGES\userdata.img')
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: DEBUG: Trying get filesize, calling fseek()
15:34:36: DEBUG: Found 'D:\copy_ofp\flash_bin\IMAGES\userdata.img' (2920740 bytes)
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...

15:34:36: {ERROR: sparse_open:2625 Unknown chunk type cac2

Did you change sparse parameter for userdata.img from true to false into rawprogram0.xml file ?

For the super.img, that's just a warning, not an error.