- Nov 28, 2021
i just uninstalled magisk from the app, and my phone is just restarting and not turnin on!
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.
Good to know. In fact, I still keep that Alpha apk and my corresponding patched boot.img (just in case)
On telegram he posts the source.zip: 76ddfeb9-alpha.zip and the standalone.apk: app-release.apk, as the latest example.
Update channel points to JSON file in GitHub repo. Last pushed was 558710bb-alpha-2 (synced with Canary v23016, Stub v23) of 10 days ago, here:
I had mentioned the source as I was posting re. builds not pushed to vvb2060's GitHub repo.
Few things to note: You really need to read release notes before using any Magisk build, official or otherwise.
Do you mean Are root-related execution environment changes hidden from the app? If so, that depends...
Note a major difference between TJW denylist and Alpha denylist:
A LOT of config is stored in the settings. For example:
settings put global "window_animation_scale" "0.5";
Current State>Settings>Generate Set All
Broken in current released builds. Fix merged in Magisk master repo downstream for S21
Nb. Standard procedure is to flash patched firmware file as AP + HOME_CSC + BL + CP as per instruction: