How To Guide [Chinese Version] Install RMX3301 Global stock firmware from Chinese
- Thread starter myogui
- Start date
You can try now to relock bootloader with this tutorial. Just download apk attached to this post and follow the steps in FAQ.
I didn't try it, but I suppose no, since realme released this apk also for global versions and added a tutorial for bootloader relock.
If I use this procedure to try and lock the bootloader will this erase all data I currently have installed with the global rom? I won't mind this so long as it doesn't brick the phone.
Yep, it will erase all data. And according to the reply above, this won't brick the phone.
I decided to be a guinea pig and test the procedure indicated by ObiWaan. Now you can unlock and relock the bootloader without any issues.
I'd like to thank all of the people who wrote to RealMe to request this change as I asked a few weeks ago. Public opinion can persuade companies to change!
I hope this opens up 3rd party rom opportunity for developers.
I'd like to thank all of the people who wrote to RealMe to request this change as I asked a few weeks ago. Public opinion can persuade companies to change!
I hope this opens up 3rd party rom opportunity for developers.
Hello
I have Unlocked bootloader, changed rom from chinese to global, with command " flash boot_magisk.img"
I got CTS profile match not passed
Now if i want lock bootloader with this new global rom i need flash pure "boot.img" or it doesn't matter ?
I don;t want brick my phone, thats why im asking.
I have Unlocked bootloader, changed rom from chinese to global, with command " flash boot_magisk.img"
I got CTS profile match not passed
Now if i want lock bootloader with this new global rom i need flash pure "boot.img" or it doesn't matter ?
I don;t want brick my phone, thats why im asking.
Hi, it matters, if you'll try to lock bootloader with magisk boot, it will brick the phone. And it seems, that flashing just stock boot.img is not enough, it will brick the phone anyway. Maybe flash again stock global rom to delete all root sources and after that try to lock the bootloader
on the money. Platform-tools 33.0.1 seems to be needed for it to work. It kept ending up on a bootloop when I used version 32 that was installed system-wide from Android Studio (stable). Thanks for this!
That didn't work for me. I am on a damaged image mode with device constantly rebooting.
Do you know how to turn off device or the contact of the guy who can fix it please? Thanks
Edit: Used service to get it back.
Last edited:
mz GT 2 Pro stucked in fastboot mode after 'flashing' to global rom..
after command fastboot -w i got this message:
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
is there any solution?
after command fastboot -w i got this message:
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
is there any solution?
Last edited:
Had Bootloop as well, downloaded the latest ADB files and followed your commands, but i changed the first one to boot.img as i dont want root on the phone
fastboot flash boot boot.img
downloaded ADB from this one, windows version. had a very old version which still worked for xiaomi devices but not anymore it seems^^
Google Releases Separate ADB and Fastboot Binary Downloads
Google releases the ADB and Fastboot binaries separately for download. These links are much smaller than downloading the entire Android SDK/Studio.
www.xda-developers.com
update your ADB from link in my replay. had same issue also issue with super.img
belive me, the new version of ADB made the difference, just flashed everything again like the one i also did a replay and it will work.
WARNING: some process will take very long, had to wait very long on vbmeta, one of them. just walk away and come back in like 10 minutes and magic is done. its only a 4kb file but writing took forever
no same bands thats why import a chinese version and flash global rom on it is so nice
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
if you read first post, NEVER lock bootloader or you can trow away the phone.
Gpay had issues as well, installed the boot-magisk.img version, downloaded magisk, installed and then did google search for universal fingerprint fix gpay, lead to the forum here as well. So now all works fine for me. If i want i can even give super user to programs now ^^111Ok so for anyone struggling, here is what I did to flash 3300 to 3301 Global & root A.16 w/safety net. I hope myogui can update original post because many of us are puzzling pieces of information from different sources. Credits to @myogui, @hacls and Shato from 4pda.to forum
If you unlocked bootloader Widevine will be L3. Some had luck contacting Realme support to fix it. I do not know if locking bootloader sets it back to L1. I think it also does not matter if you are root or nonroot, you will go down to L3 either way.
To check Widevine level, you can use app DRMInfo
1. Install USB fastboot drivers.
2. Run the deep testing apk, and after it's approved let it go into bootloader mode.
3. Connect phone to PC. If fastboot shows "waiting for devices", exit, go into Windows Update and check for updates. Then go to Optional Updates and select & install Android Google driver. (Windows 10-11)
4. Complete the unlocking of bootloader with fastboot flashing unlock
5. Download the Global rom from @myogui post and put in the same folder as the platform-tools where your fastboot is. Sometimes the super.img gets renamed to super-001.img, so change name back to super.img
6. Follow flashing like below credit @hacls. You can also run fastboot getvar current-slot to check which partition is active before running fastboot --set-active=a
If you are flashing non-root, flash "boot.img" ; otherwise flash "boot-magisk.img"
When flashing super.img, error message will display "Invalid sparse file format in header", this is OK, leave it running.
After flashing ROM, do not relock bootloader unless you don't care about root. Once you lock it, some people say Realme deeptesting apk does not accept RMX3301 (Global), and then you may have to rely on workarounds to unlock it again if you plan to root it in the future.
Optional steps to update to A.16 and root:
7. After flashing global, run the update. Currently most up-to-date version is A.16.
This will overwrite boot.img, so if you flashed with root, Magisk will be gone - no worries.
You will have to disable system updates to keep the root if Realme releases newer ROM, or wait until someone extracts newer software and patches boot.img. (or you could extract and patch yourself)
8. If you want to root the A.16:
Once OS is updated to A.16 Global, reboot back to bootloader (if you have ADB debugging enabled in Developer Options, run adb reboot bootloader, otherwise you can do the Power + volume down method)
Download bootA16magisk.img from the link below. This is patched boot.img for A.16 version
https://drive.google.com/drive/folders/1eC3okohfoTVQJBJvnIHyFUvHvV1ZDi2O?usp=sharing
8.a Run fastboot getvar current-slot .
- If it shows boot B partition, run fastboot flash boot_b bootA16magisk.img
- If it shows boot A partition, run fastboot flash boot_a bootA16magisk.img
8.b Reboot device
8.c Complete Magisk app install
Install Magisk modules (you have to copy .zip files):
safetynet-fix-v2.2.1
Shamiko-v0.4.4-106-release
Both are in link above but you can download them elsewhere
8.d Activate Zygisk in Magisk
8.e Go to configure DenyList and add in any apps you want to hide Magisk from like banking apps.
However - Don't enable the "Activate DenyList" option! This is required by Shamiko hide Magisk module
Just adjust the DenyList.
8.f Restart phone and enjoy root
Safety Net passes with BASIC evaluation type -
7Disclaimer: 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
ORCode:fastboot flash boot boot.img
9. Run the following commands to flash all other imagesCode:fastboot flash boot boot_magisk.img
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#Uro0gLle8Yr5uRZrqoyByg4if 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 selected3I decided to be a guinea pig and test the procedure indicated by ObiWaan. Now you can unlock and relock the bootloader without any issues.
I'd like to thank all of the people who wrote to RealMe to request this change as I asked a few weeks ago. Public opinion can persuade companies to change!
I hope this opens up 3rd party rom opportunity for developers.2
