[Realme GT Master Edition] enonaw:
DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE

I've just unbricked an RMX3474 (Realme 9 5G with unlocked bootloader) using this method. It was bricked (bootloader boot loop) following a bad downgrade by mistake from RUI4 to RUI3 (there's actually no RUI4 ROM available in .ofp format for the RMX3474GDPR).

QPST/QFIL is a powerful (and therefore dangerous) tool, which is why in my opinion it should be reserved for hard unbrick, i.e. for smartphones that only have access to EDL (Emergency DownLoad) mode. I think its current democratisation is not a good thing. This remains my humble opinion, of course. For a soft bricked smartphone, I'm still looking for a "fastboot" solution. LOL, that's just common sense :)

So (

I call back : unlocked bootloader needed

).

1. Download the lastest android-tools : here

2. Download the OTA update for the last stock ROM installed on the smartphone :

2a. realme-ota

2b. Type the command :

realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.firmware.XX_0000_000000000000 RUI_version region

2c. Where : - -i IMEI1 IMEI2 = for your smartphone (optional), firmware = letter of firmware, XX = number of firmware, RUI_version = 2, 3 or 4 and region = your smartphone region

2d. For example, for my smartphone, the last "F" firmware, RUI4 and EUEX region :

realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.F.00_0000_000000000000 4 01000100

2e. Result of the command is : "foreign_my_manifest_RMX3363_11.F.07_3070_202305171723.44.71d53b2c_1_cf16f9cb6b61168cd0959cff607e3b32"

2f. You'll find the download link for the OTA update in the result, just below this line

3. Extract .img files from payload.bin :

3a. payload-dumper-go

3b. Type the command :

payload-dumper-go /path/to/payload.bin

4. Put all files in the same directory (android-tools & extracted payload .img files)

4a. Example for RMX3363GDPR-F07 :

View attachment 5935761

5. Boot your smartphone into bootloader and connect it to the PC USB port

6. You need to enter fastbootd mode (to be authorised to flash critical partitions), so open a terminal and type the following command :

fastboot reboot fastboot

7. Begin with slot a :

fastboot --set-active=a

8. Start the flash of the .img files

(the number of .img files may vary depending on the smartphone model and the version of OTA update)

:

fastboot flash file1 file1.img
fastboot flash file2 file2.img
fastboot flash file3 file3.img
(... etc)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img

9. Switch to slot b :

fastboot --set-active=b

10. Relaunch the flash of the .img files

11. Switch slot a back to active :

fastboot --set-active=a

12. Reboot the smartphone :

fastboot reboot

Note : I had 2 errors during the flashes (1 on slot a, 1 on slot b, not the same). On slot a, "Writing 'modem_a' FAILED (remote: 'Operation not permitted')". On slot b, I can't remember (a problem of insufficient space for a file). I tried several things but couldn't get round these errors. Nevertheless, the smartphone rebooted correctly with RUI4 ;)

After that, you can easily patch boot.img and vendor_boot.img (optional) files with Magisk, flash them again via fastboot and obtain root mode.

Have a nice day ! :cool: