Question Rooting OneUI4 / Android 12? - Samsung Galaxy S21 Ultra

Hi Guys
Has anyone tried this yet? Is there a guide? I took a look and cant find any information on it.
FKO

I made the update and tried Magisk. The mobile phone starts up, but root is not available and Bluetooth does not work either.

fkofilee said:
Hi Guys
Has anyone tried this yet? Is there a guide? I took a look and cant find any information on it.
FKO
Click to expand...
Click to collapse
maxxd1995 said:
I made the update and tried Magisk. The mobile phone starts up, but root is not available and Bluetooth does not work either.
Click to expand...
Click to collapse
I had the same issue you need to use magisk canary version to patch the file for now until the support is added to the stable release of magisk

stephen.brader said:
I had the same issue you need to use magisk canary version to patch the file for now until the support is added to the stable release of magisk
Click to expand...
Click to collapse
Thanks for the tip. With the canary, root works. but bluetooth still not. Did you behave the same

I figured it out myself. I had to disable the "Bluetooth Library Patcher" module.

I am planning on to unlock bootloader only. Have not updated to One UI 4.0. Will I continue recieving official updates from Samsung and able to install them (not flashing that, OTA ones). I am not going to flash custom recovery or kernel or even custom rom. Will it work that way?

maxxd1995 said:
Thanks for the tip. With the canary, root works. but bluetooth still not. Did you behave the same
Click to expand...
Click to collapse
No bluetooth is working for me but it could be one of my magisk modules patches the bluetooth so I suggest try installing bluetooth library patcher module thats for fixing bluetooth on rooted samsung devices. I dont have this module but maybe one of my modules includes it im not sure:
BluetoothLibraryPatcher - Fix bluetooth pairings loss [Android 13/12/11/10/Pie/Oreo/Nougat]
Bluetooth Library Patcher • Description : This patch attends to avoid losing bluetooth pairings after reboot or airplane mode switch on rooted samsung devices. It patches on the fly the bluetooth library and should support most of samsung...
forum.xda-developers.com

stephen.brader said:
No bluetooth is working for me but it could be one of my magisk modules patches the bluetooth so I suggest try installing bluetooth library patcher module thats for fixing bluetooth on rooted samsung devices. I dont have this module but maybe one of my modules includes it im not sure:
BluetoothLibraryPatcher - Fix bluetooth pairings loss [Android 13/12/11/10/Pie/Oreo/Nougat]
Bluetooth Library Patcher • Description : This patch attends to avoid losing bluetooth pairings after reboot or airplane mode switch on rooted samsung devices. It patches on the fly the bluetooth library and should support most of samsung...
forum.xda-developers.com
Click to expand...
Click to collapse
I figured it out myself. I had to disable the "Bluetooth Library Patcher" module. thanks

Just checking - same method as A11 on the S21 Ultra?
IE - 2 files to patch with Magisk / Patched Kernel in Userdata on Odin?

fkofilee said:
Just checking - same method as A11 on the S21 Ultra?
IE - 2 files to patch with Magisk / Patched Kernel in Userdata on Odin?
Click to expand...
Click to collapse
did you manage to get root?

80s Baby said:
did you manage to get root?
Click to expand...
Click to collapse
i try also this method and bootloop still no work

i think we need new canary magisk or new twrp or multidisabler

Related

Viper4Android drivers vs compatible mode

I am on the latest MM release & kernel to hide unlocked boot loader, rooted with Magisk SU and hidden to use Android pay. I currently run Magisk module for V4A. I have been trying to get V4A to work with installed driver, but after trying several methods suggested in V4A and Magisk forums, it will only work in compatible mode with standard Google play music app. It will not work at all with Pandora or Amazon music player apps. I am not sure what compatible mode means other than it hides the driver information, so I assume it is functioning without driver (?) somehow, with lower quality results? Ultimately would like to get it to work with Pandora, my go to music source, with or without Magisk module interface. I am not sure what the Magisk module is doing if anything as the V4A works the same with the module uninstalled. Thanks if anyone has experience to share.
jrmt077 said:
I am on the latest MM release & kernel to hide unlocked boot loader, rooted with Magisk SU and hidden to use Android pay. I currently run Magisk module for V4A. I have been trying to get V4A to work with installed driver, but after trying several methods suggested in V4A and Magisk forums, it will only work in compatible mode with standard Google play music app. It will not work at all with Pandora or Amazon music player apps. I am not sure what compatible mode means other than it hides the driver information, so I assume it is functioning without driver (?) somehow, with lower quality results? Ultimately would like to get it to work with Pandora, my go to music source, with or without Magisk module interface. I am not sure what the Magisk module is doing if anything as the V4A works the same with the module uninstalled. Thanks if anyone has experience to share.
Click to expand...
Click to collapse
You have to get V4A magisk, audio modification library and universal deep buff remover (this one you might have to get from the xda thread, the one in the magisk repo seems to be broken) to get viper4android to process in all apps in normal mode.
zys52712 said:
You have to get V4A magisk, audio modification library and universal deep buff remover (this one you might have to get from the xda thread, the one in the magisk repo seems to be broken) to get viper4android to process in all apps in normal mode.
Click to expand...
Click to collapse
Thank you for responding, I did try both of these fixes by ahrion, plus he later put out his own magisk v4a module with the fixes incorporated in it, unfortunately no changes, I am wondering if it is something specific to the DT as I have never read of anyone running v4a in normal mode on a turbo.
jrmt077 said:
Thank you for responding, I did try both of these fixes by ahrion, plus he later put out his own magisk v4a module with the fixes incorporated in it, unfortunately no changes, I am wondering if it is something specific to the DT as I have never read of anyone running v4a in normal mode on a turbo.
Click to expand...
Click to collapse
I've been running that setup I described for a month now and it's survived rom updates as well, never had any trouble with it. Did you get the universal deep buff remover from the xda thread or within magisk manager?
zys52712 said:
I've been running that setup I described for a month now and it's survived rom updates as well, never had any trouble with it. Did you get the universal deep buff remover from the xda thread or within magisk manager?
Click to expand...
Click to collapse
I wasn't sure of source so just loaded deep buff remove from xda thread. Also running the audio mod v 1.4. After reboot neither Google play music or Pandora worked in compatible mode, rebooted to normal mode and no processing from either source. I removed deep buffer mod via his deep buffer restore mod, now Google play music back to running in compatible mode only. Thanks for trying to help me not sure what's different from your setup

Viper4Android Pie Compatible???

As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.
bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?
recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try
I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share
old legacy magisk module has been working for months and months.

Problem with bluetooth

Hi all.
My G873F Bluetooth disconnects upon pairing, then I have to pair it again. The problem has been the same on 10 as well as android 9. I have the libsecure storage magisk module installed but I still have to pair Bluetooth twice everytime it connects. Any help ?
Thanks
That happened to me after I updated firmware and forgot to deactivate libsecure module from magisk before update.
I had to update again without this module and after update I flashed module again and everything worked
putti71 said:
That happened to me after I updated firmware and forgot to deactivate libsecure module from magisk before update.
I had to update again without this module and after update I flashed module again and everything worked
Click to expand...
Click to collapse
Ok ? I will keep that in mind next oneui update. Cheers
Update: fix was to use this module instead. :silly:

New Issue: Paired Bluetooth Devices Gone After Every Reboot

Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
One very simple solution....only one that works.
Flash back stock rom.. and try process again. If it doesnt work....then obviously rooting or magisk is corrupting some partition. So only way to fix this is stay stock...
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Thanks for your advice.
I found the module in Magisk and it does work!
yomama163 said:
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Click to expand...
Click to collapse
I'm using a Samsung Galaxy Note 10 Plus (SM-N975) running One UI 3.1 on Android 11.
I rooted my phone with Magisk and experienced this same problem.
After installing the Magisk Module 'Bluetooth Library Patcher' by 3arthur6 and that solved the problem.

Sky go help needed to hide root with magisk

On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine
yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.
Hast everyone a sollution for running the sky Go App on rooted phones?
Skygo doesnt Work... hast anyone a sollution?
eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com

Categories

Resources