[STOCK][FASTBOOT][IN] Fastboot Flashable Images For RealMe X3 SuperZoom - Realme X3 SuperZoom Guides, News, & Discussion

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.

Related

Fix Current Image (Boot/Recovery) Destroyed!

I want to install a custom rom but some how boot image break please help me guys. I am so worried
ok here are steps !
djdreamerr said:
I want to install a custom rom but some how boot image break please help me guys. I am so worried
Click to expand...
Click to collapse
-Connect phone in fastboot mode with usb cable
-by long pressing volume down with power button together
-enter these commands
- fastboot erase userdata
-fastboot format userdata
download stock rom system.img file (will be around 2-4 gb in size) by googling on realme xt system image.
and also download boot.img and twrp recovery images like this from googling.
-fastboot flash system system.img
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
after this go to recovery mode by changing modes with volume buttons in fastboot mode.
now u can install stock rom by downloading the stock rom of the version system.img u flashed now.
I ran into the same problem last night, I restored my phone back to stock rom today. I've uploaded the extracted C03 firmware for anyone whose run into the same problem. Just flash using fastboot and you'll able to restore your phone too
Code:
https://mega.nz/file/BQIRgQqS#SvwoR1D7gtaJZlDzCu_ezXdcH_ZtRfgcqnobCTNiGaU
sepzo said:
-Connect phone in fastboot mode with usb cable
-by long pressing volume down with power button together
-enter these commands
- fastboot erase userdata
-fastboot format userdata
download stock rom system.img file (will be around 2-4 gb in size) by googling on realme xt system image.
and also download boot.img and twrp recovery images like this from googling.
-fastboot flash system system.img
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
after this go to recovery mode by changing modes with volume buttons in fastboot mode.
now u can install stock rom by downloading the stock rom of the version system.img u flashed now.
Click to expand...
Click to collapse
THANKS DUDE YOU SAVE MY LIFE :good:
I AM GLAD YOU POST THIS
djdreamerr said:
THANKS DUDE YOU SAVE MY LIFE :good:
I AM GLAD YOU POST THIS
Click to expand...
Click to collapse
You welcome bro, Now using Samsung S10 Lite
(Boycottchina Movement )
I finally decided to root my phone today and unlocked the bootloader with all the excitement, but ran into this "boot/recovery destroyed" problem. All I did was flashing Orangefox image and installed magisk. I did some digging on google and found out, two things fixes it. 1) flashing the stock recovery, and then 2) flashing vbmeta.img with the commad "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img". It actually solved the problem for me and now I'm back to orangefox and magisk works real good. There's no need to download an entire os for this fix. Nearly wasted 2gb of data on downloading the stock firmware, while I found this fix
Works Like a charm
salaigeethan666 said:
I finally decided to root my phone today and unlocked the bootloader with all the excitement, but ran into this "boot/recovery destroyed" problem. All I did was flashing Orangefox image and installed magisk. I did some digging on google and found out, two things fixes it. 1) flashing the stock recovery, and then 2) flashing vbmeta.img with the commad "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img". It actually solved the problem for me and now I'm back to orangefox and magisk works real good. There's no need to download an entire os for this fix. Nearly wasted 2gb of data on downloading the stock firmware, while I found this fix
Click to expand...
Click to collapse
This works like a charm. Just flash TWRP again and vbmeta with above command and reboot.
get required files from here.
https://forum.xda-developers.com/realme-xt/how-to/rooting-stock-rom-realme-xt-color-os-t3998271
lost recovery
[email protected] said:
This works like a charm. Just flash TWRP again and vbmeta with above command and reboot.
get required files from here.
https://forum.xda-developers.com/realme-xt/how-to/rooting-stock-rom-realme-xt-color-os-t3998271
Click to expand...
Click to collapse
my realme xt also got breaked. then as u said i flashed latest twrp and then vbmeta with given cmd, tried to boot to recovery. nothing happened. then tried to power off and on, got into working realme rom. fastboot is working but unable to boot to recovery. in fastboot bootloader status shows unlocked. tried to flash twrp img again but yet no recovery.
surajak said:
my realme xt also got breaked. then as u said i flashed latest twrp and then vbmeta with given cmd, tried to boot to recovery. nothing happened. then tried to power off and on, got into working realme rom. fastboot is working but unable to boot to recovery. in fastboot bootloader status shows unlocked. tried to flash twrp img again but yet no recovery.
Click to expand...
Click to collapse
Hey there,
It would be great if you could attached any error messages. Or what you exactly encountered after flashing vbmeta. For easy comm. you can contact on t.me/tempKChannel
Bricked my phone today and found this thread, thanks for everyone for providing solution!
My bootloader locked realme xt is displaying only the logo. No way to go to recovery, system or fastboot mode. Is is possible to still do something about it? I live in a region where there is no service center.
I've got a 8-9 month old XT with this exact issue. Phone is mint amd has always had a case and glass screen protector on it. No PC to flash files with fastboot so I ordered a POCO X3 NFC. Looking to sell it for $150 to somebody for an easy fix. Is that allowed on XDA?
I had to hire someone online to have it remotely serviced (on my PC).
Had boot/recovery destroyed message after attempting to flash a gsi. I followed the unbrick guide. I can access fastboot & boot into recovery, however touch input is not working so I'm unable to do anything. Phone sticks on the realme screen when attempting to let it boot. Any ideas? I live in the US so a service center isn't possible.
{
"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"
}
When to use?
-> If first time custom recovery installation is messed up because forgot to intall vbmeta_disabler in Recovery.
-> If you messed up and now stuck on fastboot mode and cannot go to recovery or system.
-> When your device is automatically rebooting to fastboot every 10-15 seconds.
-> Can also be used if you get a boot destroyed screen on trying to reboot to system and recovery.
How to use?
-> Download your vbmeta.img file of your device and put it inside your ADB or Platform Tools folder
-> Open CMD in ADB (You know it)
ADB commands :
Type "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" (Don't press enter yet)
->Connect Usb to PC and long press device's volume down and power button to go to fastboot mode ( In some cases Fastboot mode remains only for few seconds)
->When you see fastboot mode in your Smartphone then you press ENTER in your PC
->If you see "success" in cmd then you can reboot to your custom recovery
dalda123 said:
View attachment 5444009
When to use?
-> If first time custom recovery installation is messed up because forgot to intall vbmeta_disabler in Recovery.
-> If you messed up and now stuck on fastboot mode and cannot go to recovery or system.
-> When your device is automatically rebooting to fastboot every 10-15 seconds.
-> Can also be used if you get a boot destroyed screen on trying to reboot to system and recovery.
How to use?
-> Download your vbmeta.img file of your device and put it inside your ADB or Platform Tools folder
-> Open CMD in ADB (You know it)
ADB commands :
Type "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" (Don't press enter yet)
->Connect Usb to PC and long press device's volume down and power button to go to fastboot mode ( In some cases Fastboot mode remains only for few seconds)
->When you see fastboot mode in your Smartphone then you press ENTER in your PC
->If you see "success" in cmd then you can reboot to your custom recovery
Click to expand...
Click to collapse
i can't enter recovery and fastboot mode what should i do
He
Nightmareverified said:
i can't enter recovery and fastboot mode what should i
Click to expand...
Click to collapse
Nightmareverified said:
i can't enter recovery and fastboot mode what should I do
Click to expand...
Click to collapse
Hey bro did you the find the way to go to fast boot mode
dalda123 said:
View attachment 5444009
When to use?
-> If first time custom recovery installation is messed up because forgot to intall vbmeta_disabler in Recovery.
-> If you messed up and now stuck on fastboot mode and cannot go to recovery or system.
-> When your device is automatically rebooting to fastboot every 10-15 seconds.
-> Can also be used if you get a boot destroyed screen on trying to reboot to system and recovery.
How to use?
-> Download your vbmeta.img file of your device and put it inside your ADB or Platform Tools folder
-> Open CMD in ADB (You know it)
ADB commands :
Type "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" (Don't press enter yet)
->Connect Usb to PC and long press device's volume down and power button to go to fastboot mode ( In some cases Fastboot mode remains only for few seconds)
->When you see fastboot mode in your Smartphone then you press ENTER in your PC
->If you see "success" in cmd then you can reboot to your custom recovery
Click to expand...
Click to collapse
bro you were god to me for a period of time you have some real og skills i dont know how many peoples problem you have solved but you solved mine my phone was dead from one week now its alive once again thank you pixel expirience im good with stock rom
sepzo said:
ok here are steps !
-Connect phone in fastboot mode with usb cable
-by long pressing volume down with power button together
-enter these commands
- fastboot erase userdata
-fastboot format userdata
download stock rom system.img file (will be around 2-4 gb in size) by googling on realme xt system image.
and also download boot.img and twrp recovery images like this from googling.
-fastboot flash system system.img
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
after this go to recovery mode by changing modes with volume buttons in fastboot mode.
now u can install stock rom by downloading the stock rom of the version system.img u flashed now.
Click to expand...
Click to collapse
Simple flash vbmeta fastboot flash vbmeta.img 100% fix your destroy problem
Does anybody have solution of the current imgae (bootlrecovery) have been destroyed and can not boot of one plus 8 i m ready to pay i just need the flash rom and stock rom of one plus 8

Successfully unbricked mi 9t

I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone. ☺☺☺
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
if u could access your phone via fastboot / adb then it wasn't a hardbrick , just a softbrick
TahmidZee said:
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
Click to expand...
Click to collapse
You should check first the driver of your computer. Make sure you have the driver of your phone to your computer. After that you can check your device via adb by using commnd on cmd "adb devices".
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Can u please explain it. I am stuck with the same problem. I got success in flashing fastboot rom via miflash tool but it's still stuck in fastboot.
Thanks God Bless You.
---------- Post added at 05:01 PM ---------- Previous post was at 04:36 PM ----------
Deaddo6 said:
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
Click to expand...
Click to collapse
This Helped You guys are angel
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
fastboot boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
dix93 said:
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
flash boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
Click to expand...
Click to collapse
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Wolfcity said:
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
Click to expand...
Click to collapse
Thank you. Actually I was confused in the transcript here, I meant fast boot instead of flash.
But I figured out to use XiaomiFlash Tool to install a ROM via fastboot, and then reinstall a recovery.
The popup camera is not working good with the XIAOMI official rom (It tries to close the cam even if it is already closed). Now I'm trying to install Havoc OS to try to solve those problem, but it demands me the miui v11.0.4 or new (error in twrp), even if I have the miui v12.... trying to figure out why
for the guys whome are stuck on fastboot, you may try "XiaoMiTool V2". this bought my Mi9T from fastboot to life.
make sure all the drivers are installed as well. what's better is install usb drivers, reboot computer, enable usb debugging, connect the phone to computer, select transfer data, wait till the computer completely setup your phone, turn off phone and connect to computer, wait till computer detects and setup, put the phone on fastboot mode and connect, check whether computer shows android device... once everything are confirmed then proceed with flasing.. :good::good:
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
This command - fastboot flash vbmeta worked.
(using a version from Redispade for Grus - mi9se)
Unbricked my bootloop (recovery) after upgrading from miui 12 (android 10) to 12.5 android 11.
thanks!

TWRP on DOOGEE N20PRO

Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
DragonPitbull said:
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
Click to expand...
Click to collapse
Cool This helps already a lot.
i unlocked the Bootloader properly, but then i got a partition error. I assume i´ve an error in the command line. The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
beinfo said:
The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
Click to expand...
Click to collapse
Try but REMENBER I am not responsible for any errors. Bootloader should unlocked by adb-fastboot!!
Spoiler: Instructions
1. You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options: reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
2. Device in fastboot
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
vbmeta file from stock ROM or pulled from device
3.
Code:
fastboot -w
4.
Code:
fastboot reboot fastboot
(you MUST be at the FASTBOOTD menu now. If not, you will not be able to flash the GSI successfully)
5.
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
6.
Code:
fastboot delete-logical-partition product
- deletes the product partition, allowing a larger system partition
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
6A. fastboot resize-logical-partition product 509344768
6B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
7.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
8.
Code:
fastboot -w
for confirm great & fast start GSI
9.
Code:
fastboot reboot bootloader
9A.
Code:
fastboot erase userdata
for confirm and boot clean
10. Reboot to system
Code:
fastboot reboot
Enjoy
I also have an N20 Pro which I received Dec 2020. Had some trouble setting it up. I got the OEM ROM from Doogee customer support and was able to extract the boot image and patch it with Magisk. I then burned it with the SP Flash tool. It wouldn't boot until I burned a special vbmeta.img to turn off encryption. Now it's working fine.
Sorry this doesn't help you with TWRP but I think most people looking for TWRP are really looking to root their phone.
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
Okay so what ive seen is that you should avoid flashing custom roms via adb fastboot especially with our doogee phones, and also there are many incompatiable roms so what you will need is to unlock bootloader and do the whole twrp install thing adn also install magisk
before hand install treble info from google playstore and take down the information "arm64 a/b" and search for roms with that information to install custom os/rom/gsi properly. GSI versions are more preferred if your phone supports treblle
if your twrp keeps getting wiped after reboot open file :mount your system and connect to pc via usbcable (mtp if not showing disable mtp and re- enable it )
now got to where build.prop is saved there will be a file called recovery from boot.p , copy the file to pc , open with notepad, remove everything , save and copy back to phone (overwrite)
then go ahead and install magisk
make sure your magisk is working install edxposed, riru core , and busybox ndk get the apps you need for them (edxposed manager...) and then instal and activate a module which you can test if its working(if framework is active in edxposed manager and the module working correctly then you can go ahead and
Install custom os through twrp
follow these instructions ( https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/ ) with your custom rom (corvus, havoc, lineage...
(the g-apps didnt flash for me (error code 64) but i just rebooted and everything was working fine (including gapps but camera sucked (doogee's rear camera setup was just terrible))
https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/
** i can confirm follow instructions properly and it should work (i used this pixel experience on my doogee n20 make sure you unzip the .xz file and youre flashing a .img file
**also make sure its the gsi file (

Root and install custom recovery on realme 7 A.87 stock

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.

How To Guide [Chinese Version] Install RMX3301 Global stock firmware from Chinese

Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: This procedure didn't work for some! Please test at your own risks!
Additional warning: do not relock your bootloader once your global rom is installed. You risk bricking your device.
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. Install rooted or not boot image
Code:
fastboot flash boot boot.img
OR
Code:
fastboot flash boot boot_magisk.img
9. Run the following commands to flash all other images
Code:
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 flash userdata userdata.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
RMX3301 Stock files: https://drive.google.com/drive/folders/1-0pNU8DMhzQJjdIMYM_khqA5ASGqWatg
Mirror: https://mega.nz/folder/kw8w1QYR#Uro0gLle8Yr5uRZrqoyByg
{
"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"
}
Can anyone confirm this worked for them?
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
logmms said:
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
Click to expand...
Click to collapse
Google pay works, safetynet passes with Magisk module (probably good if you unroot and relock the bootloader but then you'll be stuck until realme unlocks the RMX3301).
but level 3 widevine unfortunately. Also some apps do detect that bootloader is unlock even with safetynet module.
Came here to say that this is working! Got my chinese version today and wanted to give it a try right away.
If this command takes a lot of time and seems like the console froze, don't panic!
Code:
fastboot flash vbmeta_vendor vbmeta_vendor.img
Almost every command took like 20 seconds, this one took almost 200, but it finishes eventually.
Also, you may end up stuck on a bootloop. But there's an easy fix, as myogui said on another thread:
Enter recovery mode, wipe data. Enter fastboot and then run the last 2 commands again:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Now everything's working, and have been running the global rom all day flawlessly!
Does anyone know how to solve the bootloop problem? I tried the last 2 comands, Wipe Data, last 2 comands again... Flashing everything again... Nothing...
Any help would be very apreciate. Thanks.
UPDATE: It's working now.. lol... I tried flashing back to the Chinese version from myogui, still in bootloop.. Then I execute the comand "fastboot flash vbmeta vbmeta.img", bootloop... Then a tons of research... Then I downloaded a RMX3301 17.5GB .ofp file to try flashing from realme Flash Tool... Then I go to sleep... Then I woke up and just go to PC to fix this thing, but realme Tool didn't work, the Flash Tool said "CANNOT FIND CENTRAL DIRECTORY".... Then I just tried flashing here again with the files and comands above... what the hell, I'm screwed anyway... But this time worked.... LOL...
Big thanks guys!
Trying to lock again the bootloader... and then a message appears saying the flash was broken or something... now I can't even turn this thing off... Just keep flashing "realme Powered by android" screen rebooting again and again and again...
Oh my... to good to be true...
Tip: Just buy the global version.
No luck. Have tried all combinations of solutions and still stuck in bootloop. Have flashed it fresh 8 times and no luck. Also tried the last two commands above and no luck. And can't use OFP method as realme tool not updated for Gt 2 Pro
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.
try running the commands in this order
Code:
fastboot flash boot boot_magisk.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 flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot flash boot boot_magisk.img
then on your phone hit power button with start selected
Would relocking the bootloader after flashing the global brick me?
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Bnblare said:
Would relocking the bootloader after flashing the global brick me?
Click to expand...
Click to collapse
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
hacls said:
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
Click to expand...
Click to collapse
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
myogui said:
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Click to expand...
Click to collapse
Man.. I just wanna play call of duty again lol but it knows even tho my safetynet passes. the app can probably see it's L3 still. I guess I'll wait for realme to release the tool for this phone. I'm pretty sure flashing back to stock using the tool would safely lock the bootloader automatically
Bnblare said:
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
Click to expand...
Click to collapse
I tried to lock with the global ROM in it... Then this screen appears...
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
Very sorry for you mate! I updated the OP to warn about this.
Bnblare said:
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
Click to expand...
Click to collapse
ADB doesn't recognize, like I said, for now on only in EDL mode.
Well, I gave up and paid a guy to flash via TeamViewer... And as I imagined... With MSM Download Tool was five clicks and it's done... Ridiculous easy... MSM would be a amazing tool if it were accessible... Unfreaking believable... Oh my...
But, anyway, it's solved. Thanks guys.

Categories

Resources