Hello,
My realme x3 superzoom is fully bricked.
I got some luck, it is detected as qualcomm 9008
So basicall,if someone have the .mbn file and all the RAW Program and Patch files in .XML, it could greatly help me..
Anyway thanks for your help or even an advice.
Hello,
A little update.
Rn i can go in fastboot but still not in recovery
Im stuck pls help
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Please make a video...it has too many complicated step...
Mrinal Mondal said:
Please make a video...it has too many complicated step...
Click to expand...
Click to collapse
Will maybe do it in august if I have time
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
Good evening!
I've got my device bricked and i follow your guide hoping to fix it, on qfil i got errors so I try with the fastboot method, but after installing all the .img i still can't boot the phone,
Something changed anyway, before I was only able to enter the fastboot mode, now after this if I turn on the phone normally it remains stuck on the first "realme" logo, and pressing - or + can I access fastboot mode or recovery, so things are getting better but still no boot on system, before follow your guide I wasn't even able to format or flash the partition system because it was telling me it wasn't existing, now it exists, but if I try to flash a stock firmware trough fastboot it telling me that there's not enough space on device... I'm a bit stuck too! What can I try?
Bob45ultras said:
Good evening!
I've got my device bricked and i follow your guide hoping to fix it, on qfil i got errors so I try with the fastboot method, but after installing all the .img i still can't boot the phone,
Something changed anyway, before I was only able to enter the fastboot mode, now after this if I turn on the phone normally it remains stuck on the first "realme" logo, and pressing - or + can I access fastboot mode or recovery, so things are getting better but still no boot on system, before follow your guide I wasn't even able to format or flash the partition system because it was telling me it wasn't existing, now it exists, but if I try to flash a stock firmware trough fastboot it telling me that there's not enough space on device... I'm a bit stuck too! What can I try?
Click to expand...
Click to collapse
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Click to expand...
Click to collapse
Thanks for your reply! I format from the recovery and I repeated the steps but same problem!
Click to expand...
Click to collapse
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Click to expand...
Click to collapse
Thanks for your reply! I format from recovery and I repeated the steps but same problem!
Bob45ultras said:
Thanks for your reply! I format from recovery and I repeated the steps but same problem!
Click to expand...
Click to collapse
Be very carefull with those next command, it will wipe out completely your devices :
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
Plahad said:
Be very carefull with those next command, it will wipe out completely your devices :
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
Click to expand...
Click to collapse
I tried to do that, but it gave me an error when I was trying to erase system and cache, anyway I access fastbootd and I format from them successfully, anyway normal fastboot still can't format system partition.
After that I tried again your guide trough fastboot, re-flashed all files and it still doesn't work,
don't really know what to do, I found a stock firmware flashable trough fastboot and I tried also with that to see if it can solve the problems, but also that it fail, when I try to flash system I receive an error
Bob45ultras said:
I tried to do that, but it gave me an error when I was trying to erase system and cache, anyway I access fastbootd and I format from them successfully, anyway normal fastboot still can't format system partition.
After that I tried again your guide trough fastboot, re-flashed all files and it still doesn't work,
don't really know what to do, I found a stock firmware flashable trough fastboot and I tried also with that to see if it can solve the problems, but also that it fail, when I try to flash system I receive an error
Click to expand...
Click to collapse
Hello,
You can try to install a custom recovery like ofox
Were you on android 10 or 11 ?
Plahad said:
Hello,
You can try to install a custom recovery like ofox
Were you on
Click to expand...
Click to collapse
I'm on Android 11
I followed your steps with the fastboot way but now my phone can't enter both fastboot and recovery,is there anything i can still do?
Or I should just take it to somewhere to repair?
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
my phone just open bootloader and apply the second step but no thing repair, my phone is RMX2086 any one can help me please
Do you have the Firehose , rawprogram and patch files that you can post to try to do it by qfil ?
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
Does your guide only apply to Realme with unlocked Bootloader or to all?
Ian94y said:
I followed your steps with the fastboot way but now my phone can't enter both fastboot and recovery,is there anything i can still do?
Or I should just take it to somewhere to repair?
Click to expand...
Click to collapse
If u cant enter fastboot, i'll suggest that u either find a way arounds with QFIL or else if not comfortable go to repair it somewhere
aliabdullah1230 said:
my phone just open bootloader and apply the second step but no thing repair, my phone is RMX2086 any one can help me please
Click to expand...
Click to collapse
Hello, did u download the good firmwares for your phone ?
I have an rmx2086 too, and i managed to made it work by doing what i did with those commends
felixpaz1992 said:
Do you have the Firehose , rawprogram and patch files that you can post to try to do it by qfil ?
Click to expand...
Click to collapse
I'm sorry, I'm not currently in my home, i'll try do find those when i'll get back, in 4 months
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
thank you very much this have save me a lot of times.
my windows computer have problem with fastboot driver. i installed realme adb-fastboot driver again and again but it doesnt work, device manager still have ''question mark'' android driver, maybe windows need to be reinstall or something... i use the same pc to unlock bootloader before,
i unpack the ozip on raspbian (using raspberry pi 3 with microsd) , fastboot flash realme x 3 that i messed up before and now it work.
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
ash1337x said:
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
Click to expand...
Click to collapse
ignore twrp thing and u didn't follow everything as u have twrp u should install stock recovery
everything is cool but i have multiple super imgs what do i do?
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
Send me stock recovery please
prabal_2004 said:
everything is cool but i have multiple super imgs what do i do?
Click to expand...
Click to collapse
Yes, 4 or 5 super img files how to flash
4 or more super img files, with defrent name
Sajeevkaif said:
4 or more super img files, with defrent name
Click to expand...
Click to collapse
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
for me, i have 1 super.0 file with 2.86gb
1 super.1 file 1.95gb
and 12 super.2 files ranging 800mb to 1.8gb
what should i get for the super.img?
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
CloudChase said:
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
Click to expand...
Click to collapse
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
what should i do? i need to fix my phone
CloudChase said:
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
Click to expand...
Click to collapse
CloudChase said:
what should i do? i need to fix my phone
Click to expand...
Click to collapse
I referred to the super image size, it's unlikely that the image has just this size, anyway it doesn't hurt to try it, flash some of them and see, you can try using fastboot too.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
No, all of threm have Difrent name and size (more than a gb file)
Sajeevkaif said:
No, all of threm have Difrent name and size (more than a gb file)
Click to expand...
Click to collapse
Did you try flashing one of them?
SubwayChamp said:
Did you try flashing one of them?
Click to expand...
Click to collapse
No,
There is a tool to merge Super Image if they are split into multiple files.
Follow this tutorial to merge it. Find the exact tool from Google search and ensure it has the orange logo as seen in the video.
my bad I didn't open xda for a long time as this device doesn't have much support on xda
yea only a10 has 1 super img other ones have multiple super imgs
if ur in still in stock u can use partition backup app(needs root) from playstore to backup required img files
I'll try to upload separate img files from a11 and a12 backed up here soon