Related
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
RMX2081PU_A33_fastboot [IN]
Fastboot Commands :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Latest Fastboot :
Download
Fastboot Images For Other Realme Devices :
Github
Guide to extract Fastboot images from ozip :
Credits :
jamflux
Regards,
acervenky
FAQs
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
Stuck in boot animation window
Hi Acervenky,
Thanks for posting the fastboot flashable zip. I was able to flash all the partitions as per your post, but when I try to start the device, it keeps boot looping every 10 seconds.
1 - Tried re-enabling verity as I was going back to STOCK, by - "fastboot oem enable_dm_verity", but it said ---- FAILED (remote: 'Unable to open fastboot HAL')
2 - Tried flashing magisk patched boot.img (33 version) posted by another user. Now it does not boot loop but just keeps showing the boot screen for hours.
3 - Please help me revive the device. I am stuck!!!
4 - I cant even push any firmware file to the device for recovery firmware update option as I dont have TWRP installed
I thought I should try reenabling the
acervenky said:
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Acervenky,
Thanks for posting the fastboot flashable zip. I was able to flash all the partitions as per your post, but when I try to start the device, it keeps boot looping every 10 seconds.
1 - Tried re-enabling verity as I was going back to STOCK, by - "fastboot oem enable_dm_verity", but it said ---- FAILED (remote: 'Unable to open fastboot HAL')
2 - Tried flashing magisk patched boot.img (33 version) posted by another user. Now it does not boot loop but just keeps showing the boot screen for hours.
3 - Please help me revive the device. I am stuck!!!
4 - I cant even push any firmware file to the device for recovery firmware update option as I dont have TWRP installed
I thought I should try reenabling the
Click to expand...
Click to collapse
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Hi Venky,
I tried as suggested by you. But it keeps boot looping every 5 seconds. I tried it in the below order -
In fastboot screen
------------------------
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
in Fastbootd screen (fastboot reboot fastboot)
-------------------------
fastboot -w
fastboot erase system
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot reboot
Could it be that I am using the wrong model ROM?
Mine is RMX2085 256gb
Realme X3 Superzoom
model number :RBS0X324IN
acervenky said:
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Venky,
I tried as suggested by you. But it keeps boot looping every 5 seconds. I tried it in the below order -
In fastboot screen
------------------------
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
in Fastbootd screen (fastboot reboot fastboot)
-------------------------
fastboot -w
fastboot erase system
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot reboot
Could it be that I am using the wrong model ROM?
Mine is RMX2085 256gb
Realme X3 Superzoom
model number :RBS0X324IN
Click to expand...
Click to collapse
Which rom were you on before flashing the GSI?
Regards,
acervenky
Thanks I was able to restore the mobile after flashing the fastboot files.
I am going to try the stereo mod for my phone. Is it possible to add a mod to increase the mic volume and ear piece volume during calls?? This has been an issue since ages and the manual mod is not easy for normal users like us. Please assist!!
acervenky said:
Which rom were you on before flashing the GSI?
Regards,
acervenky
Click to expand...
Click to collapse
I want to flash recovery image
Where I can get recovery.img RMX2081 because I don't get recovery.img in the ozip file
cheth20 said:
Thanks I was able to restore the mobile after flashing the fastboot files.
I am going to try the stereo mod for my phone. Is it possible to add a mod to increase the mic volume and ear piece volume during calls?? This has been an issue since ages and the manual mod is not easy for normal users like us. Please assist!!
Click to expand...
Click to collapse
Yes it is possible to increase the mic & earpiece gains.
Regards,
acervenky
Could you please tell me what values have to be changed to increase the mic and ear piece volume for better sound levels during calls?
acervenky said:
Yes it is possible to increase the mic & earpiece gains.
Regards,
acervenky
Click to expand...
Click to collapse
Hi Acervenky,
My mobile auto updated to version 39. I was trying to install a GSI but it failed to boot.
Now, I am unable to flash the OLD fastboot files successfully.
Coincidentally I had my old ozip file (version 33) in my phone storage. But when I try to install that from the standard recovery, it says that - I am trying to install an old version firmware and then it fails the update process after that message.
I tried extracting the fastboot files for the "new 39 version" OZIP, but when I flash them it does not boot. It keeps going back to boot-loader. Does it mean that my fastboot files are not good? (I tried following your process, but not sure what went wrong)
Can you PLEASE help me with the fastboot files for the latest version 39?
Also as you are an expert, I have the following questions -
1 - HAVOC GSI Rom had installed succesfully, but it had a bug where if I place my phone in DND then it would forever mute my ringtones. So I thought I would flash back to stock and then install the GSI again. Cleared user data and cache using the following commands, full formatted using stock recovery. But somehow even after all this the GSI DND bug was retained in new installs.
Stock sound works fine, but no matter what GSI I install, it all had that bug. Is there any way I can clear all the contents using fastboot as there is no TWRP for this device. Wish we had TWRP but we dont.
fastboot erase cache
fastboot erase userdata
fastboot gsi wipe - did not work. it said I had no GSI install.
2 - Other device users were able to root thier GSI using magisk patch method. But mine never worked except in stock rom and with the magisk patched boot file that was uploaded by Sukhad (https://forum.xda-developers.com/showpost.php?p=83117333&postcount=8). Not sure if the boot file(version 39) that I used for patch was not extracted properly.
3 - One of the installs went wrong and now my phone is bricked. Your previous version helped me unbrick my phone. Could you kindly help me with the latest version fastboot files? (version 39, india)
Device is Realme X3 Superzoom (India )
https://www.realme.com/in/support/software-update
Version 39
acervenky said:
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Acervenky,
My mobile auto updated to version 39. I was trying to install a GSI but it failed to boot.
Now, I am unable to flash the OLD fastboot files successfully.
Coincidentally I had my old ozip file (version 33) in my phone storage. But when I try to install that from the standard recovery, it says that - I am trying to install an old version firmware and then it fails the update process after that message.
I tried extracting the fastboot files for the "new 39 version" OZIP, but when I flash them it does not boot. It keeps going back to boot-loader. Does it mean that my fastboot files are not good? (I tried following your process, but not sure what went wrong)
Can you PLEASE help me with the fastboot files for the latest version 39?
Also as you are an expert, I have the following questions -
1 - HAVOC GSI Rom had installed succesfully, but it had a bug where if I place my phone in DND then it would forever mute my ringtones. So I thought I would flash back to stock and then install the GSI again. Cleared user data and cache using the following commands, full formatted using stock recovery. But somehow even after all this the GSI DND bug was retained in new installs.
Stock sound works fine, but no matter what GSI I install, it all had that bug. Is there any way I can clear all the contents using fastboot as there is no TWRP for this device. Wish we had TWRP but we dont.
fastboot erase cache
fastboot erase userdata
fastboot gsi wipe - did not work. it said I had no GSI install.
2 - Other device users were able to root thier GSI using magisk patch method. But mine never worked except in stock rom and with the magisk patched boot file that was uploaded by Sukhad (https://forum.xda-developers.com/showpost.php?p=83117333&postcount=8). Not sure if the boot file(version 39) that I used for patch was not extracted properly.
3 - One of the installs went wrong and now my phone is bricked. Your previous version helped me unbrick my phone. Could you kindly help me with the latest version fastboot files? (version 39, india)
Device is Realme X3 Superzoom (India )
https://www.realme.com/in/support/software-update
Version 39
Click to expand...
Click to collapse
One of the users from X50 Pro thread mentioned the use of Realme Flash utility to restore his device to complete factory state, can you check if it is available for your device?
And about your GSI issue, some files stick even if you factory reset; the issues are different according to devices and can carry on to other roms depending on the file in question.
Regards,
acervenky
Unfortunately it did not work when I tried. But your fastboot files helped me unbrick my phone.
Right now, it says that it cannot update and it fails (as I am trying to flash 33 but my system was recently updated to 39).
I am hoping that your fastboot files (version 39) will be able to unbrick as it did earlier...
acervenky said:
One of the users from X50 Pro thread mentioned the use of Realme Flash utility to restore his device to complete factory state, can you check if it is available for your device?
And about your GSI issue, some files stick even if you factory reset; the issues are different according to devices and can carry on to other roms depending on the file in question.
Regards,
acervenky
Click to expand...
Click to collapse
This so called stock ruined my wifi, and I couldn't flash to any stock after that. my solution was gsmmafia, he helped me for only the sum of $23.
I bricked my devise and trying to restore it using fastboot mode, but I am not able to restore System and Vendor Partitions, Plz help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[email protected] said:
I bricked my devise and trying to restore it using fastboot mode, but I am not able to restore System and Vendor Partitions, Plz help me.
View attachment 5485619
Click to expand...
Click to collapse
I finally flashed stock rom after a hectic working, found an app to convert OFP file to fastboot image files conversion (latest stock rom) and then flashed using fastboot commands. But there is no system & vendor images, instead of these there are userdata and other files, I flashed the same and it's worked for me.
You can enable Auto brightness in any gsi rom..I made a special vendor.img file to enable it..
Required things:
1.unlocked bootloader.
2.working brain.
Steps:
1.Download and extract zip file from below link.
https://drive.google.com/file/d/1Bxhuj-GLByS5rf_w53mQTGK1GmnmDZzs/view?usp=drivesdk
You get 3 file vbmeta.img,vendor.img,boot.img(this file is for redmi 9 (Lancelot).do not flash those file on other phone which code name is not Lancelot)
2.flash vbmeta.img and boot.img via fastboot mood with below cmd
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
3.flash vendor.img via fastbootd mood with below cmd
fastboot flash vendor vendor.img
4. erase all userdata and boot your device .Now your auto brightness work...
Error fix:
1."file size is larger then partition size"if you get this type of Error then you need to type below cmd in fastbootd mood.
fastboot resize-logical-partition vendor 780
2.If you face any boot loop after flash and not solve it via erasing userdata the you need to flash magisk patch boot.img which you currently use:good::good:...evenif you get bootloop then first flash global v11.0.4.0 fastboot rom then follow my instruction again..
3.If brightness slider not work or headphones not detect then follow the below post.
https://forum.xda-developers.com/showpost.php?p=83635205&postcount=1
4.If you do not know how to flash gsi on redmi 9 (Lancelot) then follow below link.
https://forum.xda-developers.com/showpost.php?p=83533901&postcount=1
prove:
I provide a zip file link as attachment.unzip it and you get a video prove...
If my process work for you then don't forget to thanks me because it is free....
What have you done to the vbmeta?
koso000 said:
What have you done to the vbmeta?
Click to expand...
Click to collapse
Nothing but add some overlay file to vendor image. It is difficult now because we cannot Mount vendor image via custom recovery so I Mount it in Linux and some overlay file and give them permission that's it...
I nothing done with vbmeta.img. it is a blank file so no need to worry about it
It didn't work for me..could you share a guide to generate fix for my own vendor
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
Hi!
I cant enter the MSM Download Tool app provided in ROMs folder. Does anyone know hoy to solve it?
I need to unbrick my phone
Sorry to say that you will have to pay an Indian to recover your phone, the MSM downloader requires an authorized id
I have a similar problem: accidentally i format the system partition and now i can only enter in recovery e fastboot mode but i can't install anything roms. Is there a way to restore stock rom or force a custom rom? Thanks.
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
bro i did everything and i unbricked my phone successfully (thanks to you and that thread https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/ )
but i still have a problem that my fingerprint doesn't work and i did not backup persist.
please help me bro - Thanks in advance.
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
Hi, man.
I really need help with this one. I have a bricked device.
So, can you provide me with the twrp? I tried to install one but can't find the right one. Also, I'm stuck with this "boot destroyed" thing. Have tried to fix it--and it seems there's step in your solution above that I've tried as well (aka. flashing boot, vbmeta, super, etc.) but still can't get it work. Do you have any idea?
Cause it seems that I have to fix the boot destroyed thing first.
TIA
pls bro help me...Wipe and after that flash the ozip file?OZIP THATS mean stock rom or?
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
help plis ???
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
myogui said:
免責聲明：我不對設備變磚、SD 卡死等負責！
警告：我沒有測試這個程序，我在安裝全球版本之前備份了庫存中文版本的圖像，但我沒有將其閃回。請您自擔風險進行測試！
1.確保您的引導加載程序已解鎖
2.下載以下鏈接中提供的圖片
3.引導您的設備進行恢復（保持音量和電源直到重新啟動）
4.擦除數據
5.將您的設備引導至引導加載程序（按住音量和電源直到重新啟動）
6.將您的設備連接到PC（確保您已在PC上安裝了fastboot）
7. 從 windows 命令提示符 cd 進入包含圖像的文件夾
8.運行以下命令刷寫所有鏡像
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash 元數據 metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
快速啟動 -w
刷新 super.img 時，如果您在 header magic 處收到 Invalid sparse file format 消息，這很好。
9.然後您應該能夠引導進入系統
庫存RMX3300中文圖片：https ://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300中文圖片（備份時槽B是正確的）：https ://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
非常感謝你， 我會嘗試
wronkians said:
非常感謝你， 我會嘗試
Click to expand...
Click to collapse
Good luck mate!
myogui said:
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
I followed the steps to the letter. Still stuck in a bootloop
Moaz.Magdy said:
I followed the steps to the letter. Still stuck in a bootloop
Click to expand...
Click to collapse
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
myogui said:
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Click to expand...
Click to collapse
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
SirGustav said:
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
Click to expand...
Click to collapse
Great to hear, congrats!
thanks mate
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Addswes said:
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Click to expand...
Click to collapse
I am so close tried the same and still bootlooping for me to
Well damn. Switching to the cable from the realme gt 2 pro box fixed it weirdly!
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
wildlime said:
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
Click to expand...
Click to collapse
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
robert3892 said:
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
Click to expand...
Click to collapse
What service did you use?
I used the person in post number 8 here:
MSM Downloaf Tool for realme GT 2 Pro
Does anyone know how to access this tool? This is ridiculous, realme has no useful tool to flash their phones and the one that is useful are impossible to access... The only one that I have access was one patched for some especific Oppo phone...
forum.xda-developers.com
wildlime said:
What service did you use?
Click to expand...
Click to collapse
PM me, I'll give you the cheapest one
thank you , any body help me reup to google drive or other
empty.cad said:
thank you , any body help me reup to google drive or other
Click to expand...
Click to collapse
Up, I need it too. @myogui can you reup to GDrive?
Use Mega , 50 GB for free
Can I use this to re-flash my global device? There are some bugs with my phone and a factory reset doesn't seem to fix it.