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.
Related
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition.
The new Twrp is out now 3.0.0-1 HERE
Let me know if this helps guys and gals.
jerflash said:
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition. This never happened to me before so it must be something in the new bootloader image or boot image that is causing this.
Does anyone else see this? I was going to test downgrading the bootloader later on today to see if the block is gone but it looks like the "default password" for encryption may have changed.
Let me know guys.
Click to expand...
Click to collapse
New TWRP test builds already out there that take care of the issue.
rebretz000 said:
New TWRP test builds already out there that take care of the issue.
Click to expand...
Click to collapse
yes i see that and i am going to flash it now. i had to read through that whole thread though. i will post it above for others.
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Awesome test build! It works like a charm
havanahjoe said:
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Click to expand...
Click to collapse
this happens because you booted into Android before flashing SuperSu or disabling the recovery-from-boot
when you flash the last item, in my case it was vendor.img, i clicked volume down on my phone, and went into recovery. i then selected SuperSu2.68 and flashed that. Then rebooted.
chaco81 said:
this happens because you booted into Android before flashing SuperSu
Click to expand...
Click to collapse
That would explain it. I didn't know SuperSu took care of this. Thank you
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Yes. I use the same version.
allen099 said:
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Click to expand...
Click to collapse
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
mickyw1980 said:
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
This allows you to keep encryption?
jerflash said:
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
floepie said:
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
Click to expand...
Click to collapse
That may be true but if you don't know to do that it will wipe everything. Just always been safer to do it individually.
Sent from my Nexus 6P using Tapatalk
gts24 said:
This allows you to keep encryption?
Click to expand...
Click to collapse
Looks like it does. Is there another way to tell?
{
"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"
}
Sent from my Nexus 6P using Tapatalk
I always flash system, boot, vendor through fastboot. Sometimes I also update the bootloader and the radio if there is a newer version available. All other IMG files are not necessary. It´s true that flashing the stuff one by one gives you more control ( and a dirty flash is also great for lazy guys like me who want to keep all their Apps, settings etc. ).
johnny2678 said:
Looks like it does. Is there another way to tell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just followed your flow chart , worked here as far as I can tell as well. (proper thanks button clicked )
When I flashed this morning and entered TWRP recovery it must of tripped something as the yellow "cannot check for corruption" warning changed to a red "Your device is corrupt" message. It still only shows for a few seconds before booting like normal. I can't really try anything until I get home, but will flashing the patched TWRP and booting into it be enough to change that back to the old yellow warning? Or do I need to reflash the system/boot packages again?
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
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!
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.
Hi, here I bring you a procedure for rooting your device using Magisk and Adb. I guess there is no need to say the risks involved in doing this.
First you'll need:
1. Having installed ADB on your pc, you can use this link: https://www.xda-developers.com/install-adb-windows-macos-linux/
2. Your device must have bootlader unlocked, here the process to do so: https://c.realme.com/in/post-details/1526491339024314368
3. The corresponding boot.img (In this thread you can find attached the file for RMX3301_11 global variant) or you can extracted by yourself from the ofp file using htis script https://github.com/bkerler/oppo_decrypt
Note: During the process I encountered that fastboot commands didn't seem to work, getting the message <<waiting for device>> when unloocking bootloader on windows 11.
This problem was caused due to the lack of proper drivers, if you face this problem there is a file with the needed drivers attached in this post as well.
Now rooting process:
1. You need to install the latest stable release of Magisk on your device, which you can find here: https://github.com/topjohnwu/Magisk
2. Copy the boot image to your device
3. Press the Install button in the Magisk card
4. Choose “Select and Patch a File” in method, and select the boot image, then connect your device via usb to your PC
5. Copy the patched image to your PC, move the file inside your platform-tools folder and rename it to patchedboot.img
6. Make sure usb debugging is turned on under developer options and give permission to your PC on your cellphone after typing the command adb devices on your ADB terminal
7. Type the command adb reboot bootloader
8. Once your device is on bootloader type de command fastboot devices to make sure your device is "attached".
9. Now type fastboot flash boot patchedboot.img
10. Reboot and open the Magisk app on your phone to check everything is ok.
Aditional stuff you might find useful:
Here you can find the Universal Safetynetfix module, which is working properly: https://github.com/blog2i2j/kdrag0n.._..safetynet-fix
You just need to flash it via magisk, reboot, turn on Zygysk and reboot again.
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
{
"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"
}
arzuakay said:
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
View attachment 5651113
Click to expand...
Click to collapse
[EU model] Unlock bootloader of European model
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post. First of all, this is only for the European RMX3301...
forum.xda-developers.com
Where is the guide?
Please stop saying there is root or even bootloader unlock for the global variant. India is not "GLOBAL" aka the world, although you might like it to be.
Lol, I UBL EU Global phone with guide here on xda
Device doesn't boot anymore after flashing patchedboot.img
Ty
where is the boot.img for glabal RMX3301_11_C.13 android 13
Extract from Full OTA package.
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Magisk should work, drivers ok?
Stano36 said:
Magisk should work, drivers ok?
Click to expand...
Click to collapse
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
morphius88 said:
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Stano36 said:
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Click to expand...
Click to collapse
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
morphius88 said:
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
Click to expand...
Click to collapse
Use this command before flashing the patched boot.img and try again
fastboot set_active a
Click to expand...
Click to collapse
NumberOneDz said:
Use this command before flashing the patched boot.img and try again
Click to expand...
Click to collapse
I've tried that too, it does the same result in either slot.
The funny thing is, using "flash boot patchedboot.img" works fine but that is obviously temporary so I dont understand why it doesnt want to stick if the temporary rooted boot works fine.
Edit: see screenshot, I ran fastboot getvar all after flashing patched boot to both slots. I will flash stock boot to get back to a workable phone for now.
morphius88 said:
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Click to expand...
Click to collapse
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rapper_skull said:
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thank you for this. I think this did it. First time I had to disable verity on any phone to get root as far as I know.
I now have root and pass Safety Net.
@vanya.ag you might need to put that in your original post in case there are others that run into the same situation.