Database Info

How to unbrick redmi note 5 pro bricked by pre-ARB4 ROM downgrade

Here's the guide from the MIUI forum:
http://en.miui.com/thread-3805592-1-1.html
Reposted in case it disappears:
Yes, this is a working solution for unbricking Redmi Note 5 Global.
The credits go to @chocoml. Her/His original post is here:
http://en.miui.com/thread-3802858-1-1.html
Credits also to @br4n94 for the MiFlash portable tip.
So, how does it work?
1. Download the two files here: https://drive.google.com/drive/folders/16lQ-A175D_5DJU-YT4lbul5htgaNNw21?usp=sharing
This is a fastboot ROM v. 9.5.19.0. Note that you're downloading an operating system from the Internet. It can do anything - steal your money, eat your breakfast, run away with your girlfriend, whatever. Beware.
2. Unzip somewhere - you get a flashable fastboot rom.
3. Download miflash portable from May 2018
4. Unzip.
5. Go into the miflash folder. Find folder "mi" and rename it to something, for example "_mi"
6. Start XiaoMiFlash.exe
7. Connect the bricked phone. You should see message in windows about Quallcom interface 9008 blablabla.
8. Refresh MiFlash to see the phone on com XX
9. Selected the anti-test rom which you unzipped in (2)
10. Do a clean_all.bat
11. Wait for the flashing to finish.
You're unbricked.
Optional, but strongly recommended:
12. Restart straight into fastboot
13. Flash another ROM from a source you trust.
Cheers and thanks again to @chocoml and @br4n94 for the tips! Send them some credits!
Finally, I'd like to point out that this "solution" unbricks the phone, but does not remove the problem.
1. We still have NO access to EDL flashing using MiFlash from Xiaomi.
2. We still don't have trusted roms. While this appears to work, it may or may not do other things.
3. ARB4 can still brick you up.
I strongly suggest you keep a backup of this ROM and the MiFlash tool after you're done.
Also, it is possible that if you continute to upgrade with Xiaomi ROMS, they may "fix" something, and this method may stop working.
So if you want to keep your phone free, move on to something else, and away from MIUI.
Good luck,

Does it require the device to be opened and to be put in edl test point?

dustmalik said:
Does it require the device to be opened and to be put in edl test point?
Click to expand...
Click to collapse
no

it is can downgrade back to firmware without anti rollback if using this guide?

Can it come out of fake UBL?
Sent from my Redmi Note 5 using Tapatalk

Mi flash not recognizing fastboot rom
Mi flash isnt recognizing rom downloaded files from gdrive

Works for my redmi note 5 pro , but i don´t know wich rom an how to fla**** in this step , can someone tell me ??
Optional, but strongly recommended:
12. Restart straight into fastboot
13. Flash another ROM from a source you trust.

got an xbl error..

google drive link is ded. does anyone have a link for the files?

Redmi Note 7 Pro - Bricked (Current Device Anti Rollback is greater than this Pkg.)

I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.

Thank you for your support. I had to go to the service center as no solution could be found.

Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.

dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.

[PRELOADER][IMG][STOCK] PRELOADER Partition Binary for MERLIN (Xiaomi Redmi 10X 4G / Xiaomi Redmi Note 9)

Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?

p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy

How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there

briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.

p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.

p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?

Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.

VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...

Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.

VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...

Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?

VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.

Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?

VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...

Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.

Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me

phone not vibrate to power on after flash vbmeta for android 11 gsi

please any help , my phone "redmi 6a " , I tried to install android 11 gsi from google from this tutorial
Install Android 11 on GSI Supported Project Treble Devices
In this guide, we will show you how to install Android 11 GSI on Project Treble devices using two methods: TWRP and Fastboot Commands.
www.droidwin.com
, and flashing vbmeta.img by twrp was not clear for me as I must "select partition to flash image " as twrp says , so i flashed vbmeta.img one time as boot and another time as bootloader and then flash system.img as system and then install permissiver_v5.zip and then reboot , my phone now not powered on at all , even any logo not appear , i put it in charger and hold power button a lot but no vibration at all and also can't open twrp or fastboot as my hold on power button all it did is flash the above light led when it is in the charger , no any thing else , I think the problem is related to my mistake when flash vbmeta as i didn't know any option i must choose or what is the problem and how can i fix it please ?

You messed up your boot system.....

1. You need a PC
2. Redmi Drivers
3. USB CABLE
4. MiFlash tool and the stock ROM

Do you have MiFlash installed on your PC?

yes , it is installed , i connected the phone as you say but it is not read by the flash tool till now

Wait so has it been discovered or not

Tried different usb ports?

Keno_I said:
Wait so has it been discovered or not
Click to expand...
Click to collapse
not discovered as in this image , although in past days , it was discovered

Keno_I said:
Tried different usb ports?
Click to expand...
Click to collapse
yes

You cannot get into bootloader?

If you cant did you check if adb connects?

Keno_I said:
You cannot get into bootloader?
Click to expand...
Click to collapse
yes , i can't but i hope i use wrong program , did you see my attachment above , if this the program you say , then yes it can't read my device although i click driver and install the drivers from the program it self

Keno_I said:
If you cant did you check if adb connects?
Click to expand...
Click to collapse
adb devices not showing any device although my phone has the above tiny light circle that indicates that it is charging by the cable connected to my pc

Try fastboot devices
Or adb devices command

Keno_I said:
Try fastboot devices
Or adb devices command
Click to expand...
Click to collapse
tried them both

i want to know is the problem already is flash vbmeta as boot ?
and now what can i do ?

1. Windows PC with MiFlash Beta (!) tool
2. Download a Xiaomi Fastboot Rom
3. extract Rom to your PC
4. start MiFlash Beta tool and point to the extracted folder
5. press Vol+ & Vol- & Power on your Mi for 10 seconds and connect it to your PC while holding the buttons another second after plugging it in
6. press refresh button on MiFlash tool
7. if your drivers are installed correct, your phone should be visible on COM-Port XXX
8. press flash and hopefully it will be flashed
9. if not: try several times
10. wait until it boots to the welcome screen (around 5 mins)
now your phone should be useable again.

i will try those steps now and tell you , i thank you very much

Did it work?

Keno_I said:
Did it work?
Click to expand...
Click to collapse
no , mi flash tool can't read it but there are good and bad news , good is that from here
i could solve my problem using sp flash tool and all instructions in the above video , but bad is after that i tried to root my device using magisk patched boot image and then got infinite boot loop and also want now to solve it the same way by sp flash tool but phone restarts every 6 or 7 seconds so sp flash tool not working with me and also tried a lot of combinations of buttons to go in fast boot mode but invain so what you think i am supposed to do now

hardbricked realme 5 pro, No bootloader and No recovery

I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet

IS there any way to re unlock my bootloader ?

shrefeltony said:
IS there any way to re unlock my bootloader ?
Click to expand...
Click to collapse
Did you managed to fix it?

shrefeltony said:
I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet
Click to expand...
Click to collapse
ONLY ONEWAY TO FIX THIS IS FLASHING THE PHONE WITH EASY JTAG PINOUT METHOD

PrateekPanwar64X said:
Did you managed to fix it?
Click to expand...
Click to collapse
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.

PrateekPanwar64X said:
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.
Click to expand...
Click to collapse
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )

iPonze said:
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )
Click to expand...
Click to collapse
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.

PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
oh hi! thanks for providing a zip file. btw, how much do you pay?

can u send me the source of the RUI 2.0 firmware you got and ill try to fix it
umm download platform-tools

- Clean wipe - Flash C.14 or latest firmware (No need if already there) - Go to custom recovery terminal and write setprop ro.separate.soft 19691 - Flash Realme UI 2.0 ozip - Reboot to bootloader - Download Realme UI 2.0 vbmeta and flash it using fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - Reboot to system

PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.

maxzeroedge said:
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.
Click to expand...
Click to collapse
Oh, Thankfully I didn’t need it later as I learnt my lesson and never locked bootloader. If I want to reupload zip, How can I remove it?