How To Guide How to upgrade your rooted device to latest update (GT2 Pro Global)

Search This thread

vanya.ag

Member
Jun 24, 2022
5
4
Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.

First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.

Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.

5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
 
  • Like
Reactions: Quake94

Quake94

Senior Member
Jan 24, 2009
71
17
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.

Tested OTA-update root preserving method

If a message shows in Magisk "Stock boot image not found" when selecting "Restore Images", then below steps are required to generate backup stock boot.img on the phone. You can also uninstall Magisk and skip this step, but that may require reinstalling any extra modules.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img

The 300mb OTA update steps:
1. Go to updater and select to download update, around 300mb.
2. Use a file manager to copy /data/ota_package/OTA/.otaPackage/mymanifest(...).zip to Download or elsewhere
3. In Magisk, select to restore image. Do not restart. If you get error, read note on top
4. Go back to updater and select three dots in upper right, then Local Install
5. Select the copied mymanifest(...).zip
6. Select only Extract. DO NOT press Install when it finishes
7. Go back to Magisk and select install to inactive partition. Do not restart via Magisk!
8. Restart via software updater "Install" button!

The 5GB OTA update procedure
1. Go to Magisk and restore image. If you get error, read note above.
2. Go to updater. Try couple times, if it doesn't show a 5GB update, then use a file manager to delete /data/ota_package/OTA/.otaPackage folder
3. In OTA updater, select only Extract. DO NOT press Install when it finishes
7. Go back to Magisk and select install to inactive partition. Do not restart via Magisk!
8. Restart via software updater "Install" button!
 
Last edited:
  • Like
Reactions: Terrorigel97

shivrajsingh

Senior Member
Sep 10, 2013
200
42
Jaipur
Realme GT 2 Pro
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
 
  • Like
Reactions: dejop and Quake94

vanya.ag

Member
Jun 24, 2022
5
4
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
 

Quake94

Senior Member
Jan 24, 2009
71
17
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
 
Last edited:

Terrorigel97

Senior Member
Jul 27, 2016
65
12
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
 

Quake94

Senior Member
Jan 24, 2009
71
17
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
 

Terrorigel97

Senior Member
Jul 27, 2016
65
12
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
 

Quake94

Senior Member
Jan 24, 2009
71
17
EDIT: resolved, see bottom note.

A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.

Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.

Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.

Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.

Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.

Anyone else in a similar situation?

EDIT: LOL I fixed it 🤭. I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......

Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.

TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
 
Last edited:
  • Like
Reactions: shivrajsingh

GIutton

Senior Member
Dec 26, 2021
71
11
OnePlus 8T
Samsung Galaxy S21 FE
EDIT: resolved, see bottom note.

A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.

Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.

Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.

Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.

Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.

Anyone else in a similar situation?

EDIT: LOL I fixed it 🤭. I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......

Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.

TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?

If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
 

Quake94

Senior Member
Jan 24, 2009
71
17
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?

If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?

There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry

In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.

EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you 😅
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"

My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.

This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
 
Last edited:

GIutton

Senior Member
Dec 26, 2021
71
11
OnePlus 8T
Samsung Galaxy S21 FE
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?

For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
    1
    EDIT: resolved, see bottom note.

    A.19 update screwed something up for me.
    I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.

    Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.

    Restarted to fastboot. Fastboot works OK.
    When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.

    Manually switched active partition via fastboot --set_active to try to boot the A19.
    Phone still softloops, again, restarted back to previous slot with A18.

    Fastboot indicates unlocked bootloader.
    Not sure what got messed up, and why bootloader mode refuses to start.
    Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.

    Anyone else in a similar situation?

    EDIT: LOL I fixed it 🤭. I went to software updater, and "Install" button was displayed.
    Pressing install restarted the phone into A19 with Magisk installed......

    Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.

    TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
  • 2
    What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
    Phone will reboot and updated. Magisk working, All modules intact.
    2
    I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
    1
    Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.

    First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.

    Here the steps:
    1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
    2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
    3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
    4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.

    5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
    6. Open your adb terminal, type the command adb reboot bootloader
    7. Test recognition by typing fastboot devices
    8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
    9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
    10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
    1
    Notes:
    When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.

    Tested OTA-update root preserving method

    If a message shows in Magisk "Stock boot image not found" when selecting "Restore Images", then below steps are required to generate backup stock boot.img on the phone. You can also uninstall Magisk and skip this step, but that may require reinstalling any extra modules.
    - Copy current ROM version stock boot.img to storage
    - Open Magisk and select install -> Patch file -> Select the stock boot.img
    - Restart phone.
    This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img

    The 300mb OTA update steps:
    1. Go to updater and select to download update, around 300mb.
    2. Use a file manager to copy /data/ota_package/OTA/.otaPackage/mymanifest(...).zip to Download or elsewhere
    3. In Magisk, select to restore image. Do not restart. If you get error, read note on top
    4. Go back to updater and select three dots in upper right, then Local Install
    5. Select the copied mymanifest(...).zip
    6. Select only Extract. DO NOT press Install when it finishes
    7. Go back to Magisk and select install to inactive partition. Do not restart via Magisk!
    8. Restart via software updater "Install" button!

    The 5GB OTA update procedure
    1. Go to Magisk and restore image. If you get error, read note above.
    2. Go to updater. Try couple times, if it doesn't show a 5GB update, then use a file manager to delete /data/ota_package/OTA/.otaPackage folder
    3. In OTA updater, select only Extract. DO NOT press Install when it finishes
    7. Go back to Magisk and select install to inactive partition. Do not restart via Magisk!
    8. Restart via software updater "Install" button!