Does the Magisk Manager say yours is an A/B device?
The only difference while rooting S21Ultra running Android 12 is that you need to use Magisk Canary instead of Stable version. All the rest is the same, you can even use A11 vbmeta. Take a look in s21ultra twrp/root guide and join tg group for latest twrp.
Wait-The only difference while rooting S21Ultra running Android 12 is that you need to use Magisk Canary instead of Stable version. All the rest is the same, you can even use A11 vbmeta. Take a look in s21ultra twrp/root guide and join tg group for latest twrp.
I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
Seems you have more or less fixed this in your HELP thread, but still have issues... Of course you need to provide at least some information to get help here; you basically told us "it didn't work "
did you managed to solve that issue please help me tooErro when bild magisk
I defined the vars env and is using the lastest Android Sdk, but always getting erros
My system: Ubuntu 20.04.3 LTS in a Virtual box machine
He is the log:
./build.py ndk && ./build.py all
Note: Some input files use or override a deprecated API.
- Downloading android-ndk-r21e-linux-x86_64.zip
- Extracting NDK zip
- Patching static libs
- Building the stub app
Note: Recompile with -Xlint:deprecation for details.
Note: /media/Magisk/stub/src/main/java/com/topjohnwu/magisk/DelegateComponentFactory.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
No issues found.
make: Warning: File 'obj/local/armeabi-v7a' has modification time 1,4 s in the future
- Building binaries: magisk magiskinit magiskboot busybox
make: *** Deleting file 'libs/armeabi-v7a/magisk'
/root/Android/Sdk/ndk/magisk/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-strip:./libs/armeabi-v7a/magisk: File format not recognized
make: *** [/root/Android/Sdk/ndk/magisk/build/core/build-binary.mk:774: libs/armeabi-v7a/magisk] Error 1
make: *** Waiting for unfinished jobs....
Build binary failed!
Bit further FWIW:
Thanks for the help, really appreciated.I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
Here you have the guide:
Thread '[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)' https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-ultra-exynos.4240993/
I got little sleep last night and about to go to bed tonight.Bit further FWIW:
Pixel testers wanted.
Also, re MIUI:
Nb. PR referenced is WIP / draft ATM. PW
Good on ya doc! I was hoping some maverick Pixel user would lose some sleep to help fix this one!I got little sleep last night and about to go to bed tonight.
Had a bit of a hard time following the Magisk issues linked.
I will go though them again tomorrow after more than three hours sleep.
So a one-off Magisk build including PR 4975 to test on Pixels to find out if it:
- Allows Pixel 4a (5G) [bramble] and newer to use Magisk without disabling verity and verification on Android 12.
No need to wipe data initially.
- Non-Pixel devices that share the same issue.
- Make sure it does not break Magisk on Pixel 4a [sunfish] and older.
Along with other devices that do not have the issue and may still be on Android 11 or below.
Sound about correct.
Great news Does Denylist work for you ? I got my Exynos S21U (also BUKG) rooted with Magisk Canary all fine, but Denylist is not working (I can select apps but the settings don't stick and don't work either)....
Mine seems to be working just fine.
Thanks for your reply, is that the 23015 build ?.... just now I tried everything aside from factory reset, so that may be my last resort now..... but at least I know that it should/can work, so thats very helpful
Surprisingly I found out what these numbers and letters are. I am from a pretty long time ago, and only recently tried again to root. This is what I found when flashing (I should have seen this earlier tbh):I figured I should post this here, and I am unsure if it is even supposed to happen. My phone is a XT1952-T, so a rebranded Moto G7 Play, and I am aware that the "bad key" and "N/A" appearing after an unlocked bootloader is normal. In my case though, these letters and numbers appear instead.
This always happens after flashing the magisk_patched file. Sometimes it ends up corrupting the phone, and other times it lets me get through, but Magisk still says N/A on installed. I am using the correct boot.img that I pulled directly from LMSA.
Whether I use TWRP or fastboot to flash it, this always ends up happening. I also flash the stock firmware with LMSA before flashing so that I ensure the previous test doesn't conflict with the next one. I don't ask for a fix, I am actually intrigued on why this happens, any ideas?
Many factors...Good morning, I've updated my Samsung Galaxy Tab S5e today via OTA (LOS 19.1, MiindTheGapps, Magisk 24.3).
Although there is an addon.d script for Magisk, only the GApps were reinstalled, not Magisk. I had to do it again via adb.
What could be the reason? File-permissions of the script are fine.
libsu 5.0.0 is out!Looks like major libsu release is now imminent; most fixes are now merged.
Should see major stability improvements in Magisk and root app implementation... Should see new commits for Magisk proper again soon too!
John has made some major libsu changes (see libsu GitHub).
Here are extra comments on vvb2060 fixes from her TG (Chinese translated....
John Wu, 2h
Major libsu update 5.0.0!
Introduces a new module "nio" to perform I/O operations through root services, moving away from the error prone, inefficient shell command backed I/O the library used to provide.
It's already using splice under-the-hood. There is already some Linux magic!