Database Develop

Magisk v21 on android 11: bootloop at bootloader when flashing magisk patched img

I've been waited for Magisk v21 released by John Wu this morning, but I ran into some problems
What I've done
- download stock image file from Google official site
- follow the instruction given by John Wu at GitHub wiki
- run command
Code:
adb shell magisk --remove-modules
- when i flash the patched boot.img file, it stuck on the *G logo* with progress bar under it.
- After a certain period of time, it comes back to bootloader with a prompt saying: "no valid slot to boot".
What i've tried:
- redo all processes, no working
- switch active slot to both a & b, none working
- re-patch the stock boot.img file use different Magisk Manager version. The ones i tried: v8.0.0-Beta(offers Magisk v21), v8.0.0-Stable(offers Magisk v20.4), Canary version (offers Magisk Canary who claims to support android 11)
- change the command
HTML:
fastboot flash boot ***.img
to
HTML:
fastboot flash boot_a ***.img
&
HTML:
fastboot flash boot_b ***.img
then run
HTML:
fastboot reboot
. same result as said before
Basic info:
- Device: Pixel 3 (blueline), android 11 (build number RP1A.200720.009), latest android security update & Google play system update.
- Magisk: Magisk Manager v8.0.0 (released hours ago), Magisk v21 is suppose to be installed

Is patched boot.img filesize ~32 or ~64mb?

I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.

done

dmk16 said:
Is patched boot.img filesize ~32 or ~64mb?
Click to expand...
Click to collapse
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler

red stapler said:
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
Click to expand...
Click to collapse
Seems like we're in the same boat here lol, is this enough proof for a legit bug issue to John?

red stapler said:
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version.
Click to expand...
Click to collapse
DaddyTony said:
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
Click to expand...
Click to collapse
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
[MagiskBoot] Pad boot images to original size with zeros
Click to expand...
Click to collapse

nogaff said:
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
Click to expand...
Click to collapse
Glad to hear, hope this indicates patch is successfully done?

Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11

So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).

I forgot to mention that I didn't install or use a custom recovery, such as TWRP. Using the stock recovery.

73sydney said:
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
Click to expand...
Click to collapse
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?

Didgeridoohan said:
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
Click to expand...
Click to collapse
I forgot to mention that i run this command before install magisk patched boot.img
Code:
adb pm shell magisk --remove-modules
I didn't have TWRP installed on my device, don't seem to have TWRP for Pixel 3 on android 11.

DaddyTony said:
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Click to expand...
Click to collapse
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it

73sydney said:
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
Click to expand...
Click to collapse
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
Due to this reason, we no longer recommend installing Magisk through custom recoveries on modern devices.
Click to expand...
Click to collapse
BTW he also said the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
--------------------
edit:
Just find out Pixel 3 (blueline) has **NO** official support of TWRP v3.4+, but Pixel 3 XL (crosshatch) has it. How ironic.
and I wonder if TWRP v3.4+ support android 11?

DaddyTony said:
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
BTW he also says the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
Click to expand...
Click to collapse
Hmmm, disappointing
Ive literally tried the image patch method once, a lot of faffing about, I always use the TWRP method, easy peasy at least for older device
....we no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support.
Download the Magisk installer zip
Reboot to custom recovery
Flash the zip and reboot
Check whether Magisk Manager is installed. If it isn’t installed automatically, manually install the APK.
Click to expand...
Click to collapse
Guess ill be happy to remain a legacy device user

This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11

Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?

polyxn said:
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
Click to expand...
Click to collapse
Which version of Android?
Do you have TWRP installed?
If you do people have been posting that going to Advanced, then tapping Fix Bootloop may work
Otherwise find the boot image of the ROM you have installed, and flash that to the device
If youre on Android 11 on the Pixel, as i found out myself via bootloop, do NOT install TWRP, just fastboot to it to flash zips

M66B said:
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Click to expand...
Click to collapse
I used this command (and tried to boot in slot a), the patched img still won't boot.
Did you managed to flash Magisk with patched boot file?

How To Guide Rooting the Mi 11 with the latest Xiaomi.eu ROM

EDIT: This is not for the TWRP version. I will update this thread soon!
Hello!
Since I saw a lot of people asking, I decided to post how to root a Mi 11 (as of 2021-02-11).
Install the Xiaomi.eu ROM. You can find more details in this post. Keep the ROM's files, you will need some of them!
Connect your phone to the PC and put it into file transfer mode.
Download Magisk Manager from the official GitHub repository and install the APK. DO NOT DOWNLOAD MAGISK MANAGER FROM ANYWHERE ELSE. THIS GITHUB REPOSITORY IS THE ONLY OFFICIAL, TRUSTED SOURCE.
In the directory you extracted the ROM zip file to, there's a directory called images. This directory contains a file called boot.img. Copy the boot.img to your phone's Download folder.
Open the Settings app, go to My Device, then tap MIUI Version until it says You are now a developer.
Go back to your Settings app and use the search bar to search for USB Debugging and enable it. Click on Yes when it asks whether you want to trust this computer.
Once the file is completely copied, open Magisk Manager on your phone. There will be 2 categories: Magisk and Manager. On the Magisk category, click on Install and choose Select and Patch a File. Navigate to your downloads and select boot.img. Click on Let's go.
When Magisk has finished patching your boot.img file, it will say Output file written to /storage/emulated/0/Download/magisk_patched_XXXXX.img, where XXXXX is 5 random letters/digits.
Open a command prompt on your computer and run adb pull /sdcard/Download/magisk_patched_XXXXX.img , replacing XXXXX with the random characters Magisk showed you earlier. This will copy the file to the directory you are currently in; on Windows, if you are using cmd, this will be C:\Users\[your username].
Reboot your phone into fastboot mode by turning it off, then holding the power and volume-down buttons until it vibrates.
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b). Don't forget to replace XXXXX with the random characters Magisk Manager generated. Run the command fastboot reboot and open the Magisk Manager app when your phone has finished rebooting. The app should say that it needs to install some other components; click yes and let it do its thing. It will reboot the phone, and after that, Magisk and therefore the root should be working!
When I first did this, my SafetyNet check failed. I fixed this by repeating all the steps, except that I updated the ROM instead of reinstalling it. You can update it even if it's the same version; it will just flash everything again. You may need to clear the cache of Google Play and reinstall Google Pay if the SafetyNet check initially failed.

Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?

PandaKiller said:
Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?
Click to expand...
Click to collapse
You do not need to use the OEM Unlock option in the developer options. Mine is still off even after I unlocked my bootloader. You need to use the Xiaomi Unlock Tool found at https://en.miui.com/unlock/ .
Before using this tool, you need to log in to you Mi account on your phone. Then, reboot the phone into fastboot mode, connect it to your PC, and use the unlock tool. It will tell you to wait 168 hours (1 week) before trying again. DO NOT RETRY BEFORE THE 168 HOURS ARE OVER OR THE TIMER RESETS! Even if you are a single minute early, it will reset the timer.
Once the week has passed, do this again and your phone will be unlocked. Warning: This will erase your data.
You should prepare the boot image BEFORE unlocking, because otherwise you will have to go through the phone's setup, install Magisk, patch the image, and wipe the phone again.
Another warning: Do not re-lock your bootloader. If the bootloader is re-locked with any ROM other than the one the phone shipped with installed, the phone gets bricked.

Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.

PandaKiller said:
Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.
Click to expand...
Click to collapse
If you use the Xiaomi.EU ROM, you can update without wiping your data. They give you 2 scripts - 1 for installing and 1 for updating.

Thanks for the write-up. Worked like a charm (Y)

Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?

Giova19 said:
Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?
Click to expand...
Click to collapse
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.

Lucavon said:
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.
Click to expand...
Click to collapse
Ok noted. I rooted following the full process 3 times and cannot get the safenet.

If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!

Giova19 said:
Ok noted. I rooted following the full process 3 times and cannot get the safenet.
Click to expand...
Click to collapse
That's weird, it works perfectly fine for me. Maybe you need to re-download your Xiaomi.eu ROM.
xXSkylinexX said:
If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!
Click to expand...
Click to collapse
Yes, you need to repeat it. After updating, copy the boot image, patch it again, etc, like in this post.

Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?

Plathoon said:
Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?
Click to expand...
Click to collapse
Do you have magisk hide enabled?
If you do and you're checking safetynet status with a different app than magisk manager, you need to add it to hide.

Magisk hide is enabled too

SOLVED
- enable magiskhide
- download "magiskhide props config"
- use app like termux and follow steps :
* "su"
* "props"
* "1" (edit device fingerprint)
* "f" (pick a certified fingerprint)
* select your phone
* accept and reboot.
and now it work.

Hello,
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Note: I installed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot
After installing the Rom, the following error message appeared at the end.
fastboot: error: Cannot generate image for userdata
Can it have anything to do with it?

Lucavon said:
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b).
Click to expand...
Click to collapse
Why don't write directly fastboot flash boot_ab magisk_patched_XXXXX.img ? Is that intended ?

bert4711 said:
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Click to expand...
Click to collapse
Idk if I was having and same issues, but for me on 3.31 xiaomi.eu I was having issues with the superuser prompt not appearing. I found it happened only when the magisk app was repackaged. Approving prompts while it was unhidden then hiding magisk worked great.

Edited

I use the root explorer, the root query also appears with Magisk. But I still don't get write access to the root directory. I originally had the Global Rom V12.0.4.0.RKBMIXM on it. After the bootloader was open, I flashed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot. The following error message occurred at the end of the flash process. fastboot: error: Cannot generate image for userdata I am currently assuming that the problem with root has something to do with it. I have already tried the Version xiaomi.eu_multi_MI11_V12.5.1.0.RKBCNXM_v12-11-fastboot. The result is the same... fastboot: error: Cannot generate image for userdata and no write permissions in the root directory ...

[OOS][ALL][Stock boot][Stock recovery] OxygenOS 11.0.0

Here are all the boot.img and recovery.img of OxygenOS 11.0.0. Since TWRP isn't ready yet, I guess a lot of people need it if they didn't keep their root permissions.
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
OOS 11.0.0 EU:
boot.img
boot.img (Magisk v22 patched)
recovery.img
OOS 11.0.0 GLOBAL:
boot.img
recovery.img
OOS 11.0.0 INDIA:
boot.img
recovery.img
Please note: I'm not responsible for anything you do to your device. You use these files at your own risk. I will not provide any further .img files nor ask me for patched files. Any contribution with patched boot.img files is welcome of course. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!

Would I be able to keep my phone rooted with this after updating?

This is very useful
thanks

jman12311 said:
Would I be able to keep my phone rooted with this after updating?
Click to expand...
Click to collapse
No, unless you use the Magisk patched EU version. Otherwise always install the update, then use the Magisk Manager to patch the inactive slot and then (only then!) reboot. Then you'll keep root.
Otherwise use the stock boot.img and patch with Magisk Manager. Then flash the patched image via fastboot. There are plenty of tutorials on XDA

Hi i installed the update already but didn't reboot what is the solution to keep root ?

Janusk22 said:
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Click to expand...
Click to collapse
1. Install Magisk manager app
2. Open the app and choose "Install to inactive slot (After OTA)"
3. Reboot!

already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it

Janusk22 said:
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Click to expand...
Click to collapse
Use USB debugging and a PC with the code:
Code:
adb wait-for-device shell magisk --remove-modules
If USB debugging isn't enabled, flash the stock boot.img (without root), boot it, enable ADB debugging and allow the connection to the PC. Then flash the patched boot.img and execute the command above
That is assuming you have a OnePlus 7T Pro which doesn't have a decryptable recovery. Otherwise you can simply flash the Magisk uninstaller

But i have a error I think that i cannot write in system
I have always : cannot be accessible

Thanks i just had to run the command when i rebooted

Is just me or GPS takes more time to "fix" satellites?

FSadino said:
Is just me or GPS takes more time to "fix" satellites?
Click to expand...
Click to collapse
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.

Macusercom said:
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Click to expand...
Click to collapse
I calibrated the A-Gps again, let's see if that was it. Thank you

Hi I was wondering if you could possibly share the android 11 update file I have a Oneplus 7T Pro HD1910 currently on OOS 10.1.14 It would be awesome if you can PM me. I've tried downloading from Oygen Updater it fails at 98% also on XDA forum the download fails. I'd really appreciate it. Thanks

Macusercom said:
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
Click to expand...
Click to collapse
Hey, could you please share the payload.bin extract procedure?

Ia possible to use this files to back to stock rom from lineageos 18.1? If yes, can someone help me and give me the procedure how to do this?

For all the "EU" and "global" files, I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.

Seeking a solution to disable Zygisk from ADB or recovery

After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?

Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk

I made some progress on this.
jons99 said:
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk
Click to expand...
Click to collapse
boot1.img or boot2.img?

both I guess?
why you have 2 boot imgs?

jons99 said:
both I guess?
why you have 2 boot imgs?
Click to expand...
Click to collapse
No idea. I don't even know if they're valid anymore, since I'm on a custom rom and kernel. It's been years since I've installed this stuff, so I don't remember the specifics.

you know what you can do instead is just fastboot boot into your unrooted boot ing and open the magisk app disable zygisk and reboot this way you'll keep magisk

I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.

Bill720 said:
I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.
Click to expand...
Click to collapse
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp

jons99 said:
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp
Click to expand...
Click to collapse
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.

Bill720 said:
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.
Click to expand...
Click to collapse
if you have an old kernel you might need to flash an older version of magisk try v23 maybe

jons99 said:
if you have an old kernel you might need to flash an older version of magisk try v23 maybe
Click to expand...
Click to collapse
These results are with version 23.

ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)

jons99 said:
ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)
Click to expand...
Click to collapse
Not sure that I would've taken one of those.

well you can always patch the boot img with magisk and flash it in fastboot that always works

Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
Try this:
Turn device off
Open ADB command line
Type adb wait-for-device shell magisk --remove-modules
Connect device to USB cable and boot
This should remove modules allowing a successful boot with root.
Did you post this question on Reddit? I just answered an identical question there yesterday lol

jons99 said:
well you can always patch the boot img with magisk and flash it in fastboot that always works
Click to expand...
Click to collapse
Where could I procure a clean boot.img file? Is that part of the rom, the kernel, or something else?

usually it's inside payload.bin from within the rom zip

jons99 said:
usually it's inside payload.bin from within the rom zip
Click to expand...
Click to collapse
Interesting. I extracted the AlphaOmega Rom .zip, and found no payload.bin, but there is a boot.img file in the "kernel" folder. Should I still use that, even if I don't use the kernel supplied with the rom?

you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it

jons99 said:
you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it
Click to expand...
Click to collapse
I'll have to try that next. Now, if I could just find a working fastboot driver for this device...

How To Guide ROOT REALME GT2 (RMX3312) in 10 minutes

REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312

Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?

gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want

Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!

Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..

b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us

How to root gt 2 running on pixel os?

_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image

Thanks