Magisk General Support / Discussion

[Ralegend]

Try the A51 5G forum.

“E:[libfs_mgr]Error updating for slotselect”

Maybe this recovery mode warning is the cause. Any ideas?

 

[J.Michael]

“E:[libfs_mgr]Error updating for slotselect”

Maybe this recovery mode warning is the cause. Any ideas?

Does the Magisk Manager say yours is an A/B device?
I have never seen a reference to selecting a slot with Odin.

Have you checked the forums for the A51 5G?
Or, do you know enough about both devices to know that A51 is nothing like A52?

 

[Ralegend]

Does the Magisk Manager say yours is an A/B device?
I have never seen a reference to selecting a slot with Odin.

Have you checked the forums for the A51 5G?
Or, do you know enough about both devices to know that A51 is nothing like A52?

The Canary building only shows Ramdisk YES information.

 

[Fishballs]

Been looking around but have only found Rooting guides for Android 12 on Pixel Threads.

Is there a Specific guide to root Samsung's Android 12? (Specifically the S21 Ultra)
Or are they roughly the same.

 

[AndrzejDwo]

Been looking around but have only found Rooting guides for Android 12 on Pixel Threads.

Is there a Specific guide to root Samsung's Android 12? (Specifically the S21 Ultra)
Or are they roughly the same.

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.

Cheers

 

[Fishballs]

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.

Cheers

Wait-
So no more Patching of AP for A12?

I didn't use TWRP to root for A11, and all this vbmeta thing confuses me.

 

[AndrzejDwo]

Wait-
So no more Patching of AP for A12?

I didn't use TWRP to root for A11, and all this vbmeta thing confuses me.

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/

Cheers

 

[pndwal]

i just uninstalled magisk from the app, and my phone is just restarting and not turnin on!

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 "

From other thread I see you have Samsung phone.

FWIW, seems you missed some of the official Installation Instruction notes for Sammy:

Important Notes​

• Never, ever try to restore either boot or recovery partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
• To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
• Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.

The first point is your problem; either uninstall method in Magisk App restores boot image (either stock boot or recovery partition), and this doesn't work for newer Samsung devices. Seems you now need to follow the advice on recovering properly...

Please read official Installation Instruction page, especially Samsung section as Sammy procedures are quite different from standard & fraught. Hope it helps. PW

 

[sahil_bhandari]

Erro 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
my env:
ANDROID_SDK_ROOT=/root/Android/Sdk
PATH=/media/android-studio/jre/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

He is the log:

./build.py ndk && ./build.py all

• Downloading android-ndk-r21e-linux-x86_64.zip
• Extracting NDK zip
• Patching static libs
• Building the stub app

Note: Some input files use or override a deprecated API.
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.

Output: out/stub-release.apk

• Building binaries: magisk magiskinit magiskboot busybox

make: Warning: File 'obj/local/armeabi-v7a' has modification time 1,4 s in the future
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!

did you managed to solve that issue please help me too

 

[curiousrom]

FYI:

https://twitter.com/i/web/status/1465511242303295488

 

[pndwal]

FYI:

Bit further FWIW:
Pixel testers wanted.

Confirmed by @RikkaW it can somehow be fixed by correcting vbmeta's flags. She's having Pixel 5 Android 12 rooted permanently by Magisk without cleaning userdata. We need more people to help test now...

See here:
https://github.com/topjohnwu/Magisk/issues/4343#issuecomment-981104538
and here:
https://github.com/topjohnwu/Magisk/issues/4941#issuecomment-981104664
Also, re MIUI:
https://github.com/topjohnwu/Magisk/issues/4447

Nb. PR referenced is WIP / draft ATM. PW

 

[Fishballs]

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/

Cheers

Thanks for the help, really appreciated.
It works, got BUKG rooted (≧▽≦)

 

[Utini]

Does the latest magisk canary for Android 12 prevent deep sleep (since debug seems to be on)?

 

[moocow1452]

On the latest Canary, my Oculus Go spit out a console-ramoops that was a little garbled after the Magisk installation where a previous one was much more legible. Is there a reason for that or a method to get cleaner data?

 

[Lughnasadh]

Does the latest magisk canary for Android 12 prevent deep sleep (since debug seems to be on)?

No

 

[ipdev]

Bit further FWIW:
Pixel testers wanted.

See here:
https://github.com/topjohnwu/Magisk/issues/4343#issuecomment-981104538
and here:
https://github.com/topjohnwu/Magisk/issues/4941#issuecomment-981104664
Also, re MIUI:
https://github.com/topjohnwu/Magisk/issues/4447

Nb. PR referenced is WIP / draft ATM. PW

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.

Cheers.

 

[pndwal]

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.

Cheers.

Good on ya doc! I was hoping some maverick Pixel user would lose some sleep to help fix this one!

Sounds like on right track, but I only took cursory glances at Pixel issues recently as I'm a Xiaomi user currently... not sure of anything, but I'm sure you're the right guy to help...

I noted that MIUI w/ related issue are all late MTK devices. PW

 

[s3axel]

Thanks for the help, really appreciated.
It works, got BUKG rooted (≧▽≦)

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)....

 

[Fishballs]

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.
Using Magisk Alpha though..
Not sure if that makes the difference ouo

 

[s3axel]

Mine seems to be working just fine.
Using Magisk Alpha though..
Not sure if that makes the difference ouo

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