Develop Bugs

[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.

The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.
When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.
The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.
The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:
FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
Extra services are disabled as needed per device.
Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.
The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.
If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.
The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.
The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.
The package is attached to this posting and the code is available on GitHub.

Change log
v3.1 (2020-12-30)
Fix failure to detect a Samsung device on some versions of TWRP.
Make deprecated libbluetooth patching also work on devices originally launched on Android 9 and later updated to Android 11.
v3.0 (2020-12-29)
Add support for Android 11.
All Samsung devices running Android 9 or later are now implicitly supported.
Fix bug that caused disablement of stock recovery auto-reflash to fail on Android 10 devices.
Improve progress and error reporting.
v2.6 (2020-10-05)
Add support for the North American Z Fold2 (F916U/U1).
Add support for the A71 (A715F).
Add support for the Note10 Lite (N770F).
v2.5 (2020-09-14)
Fix issue of 2019 devices upgraded to OneUI 2.5 (DTH firmware) not booting after flashing.
Add failsafe logic for robust mounting of System partition by devices using very recent TWRP builds from the Android 10 branch (e.g. S20, N20, Tab S7 and Z Fold2).
Disable cass service on S10 and N10 series devices (required for OneUI 2.5).
Added an extra path to files searched for Vaultkeeper service disabling.
Added an extra path to files searched for cass service disabling.
Added support for the Z Fold2 (F916B/N and F9160).
v2.4 (2020-09-10)
Added support for many new 2020 devices, such as the S20 and Note20 ranges, as well as the Tab S7 and Tab S7+ ranges.
Fixed mode of patched Bluetooth library to match original.
Other minor bug fixes.
v2.3 (2020-04-11)
Support Snapdragon-based devices that have been upgraded to Android 10, such as the F900[FN] (Fold), F907[BN] (Fold 5G), T860 (Tab S6) and T865 (Tab S6 LTE), as well as Asian S10 and Note10 models.
Improve robustness of libbluetooth patching.
v2.2 (2019-12-13)
Disable wsm service to allow Samsung smartwatches to connect to Galaxy Wearable app (thanks to Andrei Seitan).
Support optional patching of system libbluetooth.so for retention of Bluetooth pairings across reboots (thanks to Arthur Trouillot).
Remove undocumented interactive mode.
v2.1 (2019-12-04)
Fix disabling of Vaultkeeper and proca in the vendor interface manifest.
Add support for N971N (Korean N10 5G).
v2.0 (2019-11-30)
Add support for Exynos-based devices upgraded to Android 10.
Add support for T72[05].
v1.7 (2019-10-20)
Add generic support for Qualcomm devices.
Support the Qualcomm S10 (G9700, G9730 and G9750), Note10 (N9700, N9750 and N9760), Tab S6 (T860 and T865) and Fold (F900F and F907B) ranges.
Add support for more Korean (N type) variants.
v1.6 (2019-09-18)
Add support for more variants of A50: A505([YG]N|G).
Fix A205G detection.
v1.5 (2019-09-13)
Added support for A10 - A50 and Tab A 10.1.
v1.41 (2019-08-28)
Added support for N976B (Note 10+ 5G).
v1.4 (2019-08-28)
Changed regex that caused too much of $ANDROID_ROOT/init.rc to be commented out by some versions of sed(1).
v1.3 (2019-08-18)
Updated to work with TWRP 3.3.1-6_ianmacd and later for the S10 range.
Added support for Note 10 and Note 10+ F and N model devices.
v1.2 (2019-06-17)
Added support for G977B (S10 5G) model devices.
v1.1 (2019-04-22)
Fixed stock recovery auto-reflash prevention.
Added support for N (Korean) model S10 devices.
v1.0 (2019-04-09)
Initial version, supporting F model S10 devices.

Will this in some way remedy the problem that when powering off the S10, it wont listen to they keycombo to boot into TWRP anymore?
If one is in system, and do a reboot all is fine, it will heed the keycombo and let you into TWRP to do what you want and then reboot->recovery to start system with root.
But as soon as the device is turned completely off, it breaks.

Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
cheers

Nextasy said:
Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
Click to expand...
Click to collapse
If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.

So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Thanks for ur time to reply and the mod.
cheers

does the disabler in the twrp thread also need to be applied? or does this replace it?

Nextasy said:
So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Click to expand...
Click to collapse
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.

tensux said:
does the disabler in the twrp thread also need to be applied? or does this replace it?
Click to expand...
Click to collapse
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.

ianmacd said:
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.
Click to expand...
Click to collapse
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot

tensux said:
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot
Click to expand...
Click to collapse
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......

ianmacd said:
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.
Click to expand...
Click to collapse
Thanks. But l can flash it after rooting with "TWRP for Galaxy S10 Magisk Prepatched by geiti94"?

dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
seems like only a very small amount of people have been able to get it to work. the procedures are more complicated than with past phones, but i wonder if there could be a very specific version of bootloader we need to have flashed, not just any of the ASCA's

dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.

PiCkLeS said:
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.
Click to expand...
Click to collapse
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.

drago122 said:
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.
Click to expand...
Click to collapse
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.

PiCkLeS said:
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.
Click to expand...
Click to collapse
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?

drago122 said:
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?
Click to expand...
Click to collapse
Yes.

PiCkLeS said:
Yes.
Click to expand...
Click to collapse
Thank you for the clarifications

drago122 said:
Thsnk you for the clarifications
Click to expand...
Click to collapse
You are welcome

Custom Kernels, SELinux Enforcing, Tincore Keymapper, and a SM-T830...

My ultimate goal here is to be able to get Tincore's Keymapper app to recognize a bluetooth controller so I can get play Call of Duty Mobile with a fricken controller again!
That being said, I'm running into roadblocks left and right, and nothing that I've tried is working out the way that I intended them to LOL
Here's the skinny:
Tablet is a Samsung Galaxy S4 Wifi SM-T830
Current firmware is 8.1.0 Oct 2018 security patch ARJ3
Bootloader unlocked and rooted (with Magisk) just the other day to install Tincore Keymapper...did that successfully.
XBone controller is paired and recognized by the tablet, but not by TKM.
I have suspicion to believe it *might* be related to the fact that SELinux is set to enforcing.
Because of Knox, or Samsung, or whatever, I can't use terminal commands to change SELinux to permissive to test this theory. (I'm not even sure this would help TKM recognize the bt controller, but figured I'd try!)
So, questions are:
1. Is it possible on the current stock kernel to change SELinux from enforcing to permissive? If so, how?
2. If the answer to Question 1 is no, Is there a custom kernel/ROM for the SM-T830 that allows one to change SELinux from enforcing to permissive built for the SM-T830?
3. Is there another viable option that I'm missing here? Is there some other troubleshooting I should try first?
4. Am I at a dead end with this, and should I stop wasting my time with all of this hullabaloo?
TIA

greevedogg said:
My ultimate goal here is to be able to get Tincore's Keymapper app to recognize a bluetooth controller so I can get play Call of Duty Mobile with a fricken controller again!
That being said, I'm running into roadblocks left and right, and nothing that I've tried is working out the way that I intended them to LOL
Here's the skinny:
Tablet is a Samsung Galaxy S4 Wifi SM-T830
Current firmware is 8.1.0 Oct 2018 security patch ARJ3
Bootloader unlocked and rooted (with Magisk) just the other day to install Tincore Keymapper...did that successfully.
XBone controller is paired and recognized by the tablet, but not by TKM.
I have suspicion to believe it *might* be related to the fact that SELinux is set to enforcing.
Because of Knox, or Samsung, or whatever, I can't use terminal commands to change SELinux to permissive to test this theory. (I'm not even sure this would help TKM recognize the bt controller, but figured I'd try!)
So, questions are:
1. Is it possible on the current stock kernel to change SELinux from enforcing to permissive? If so, how?
2. If the answer to Question 1 is no, Is there a custom kernel/ROM for the SM-T830 that allows one to change SELinux from enforcing to permissive built for the SM-T830?
3. Is there another viable option that I'm missing here? Is there some other troubleshooting I should try first?
4. Am I at a dead end with this, and should I stop wasting my time with all of this hullabaloo?
TIA
Click to expand...
Click to collapse
Depends on your current OS?

ashyx said:
Depends on your current OS?
Click to expand...
Click to collapse
Thanks for the reply @ashyx. I'm currently on 8.1.0, but I have no problem updating, if need be. Right now, it looks as though my only option for a modified kernel that has SELinux permissive ability is @Mentalmuso's WETA 7.0... Which I've been looking into, but haven't pulled the trigger yet. It would mean upgrading from Oreo to Pie, but I'm fine with that

greevedogg said:
Thanks for the reply @ashyx. I'm currently on 8.1.0, but I have no problem updating, if need be. Right now, it looks as though my only option for a modified kernel that has SELinux permissive ability is @Mentalmuso's WETA 7.0... Which I've been looking into, but haven't pulled the trigger yet. It would mean upgrading from Oreo to Pie, but I'm fine with that
Click to expand...
Click to collapse
If you know how to unpack and repack a recovery/boot image, you can use the kernel from my TWRP build. It will allow SELinux to be set to permissive.

. .

I ended up updating to Pie, and flashed a permissive kernel, which worked in getting Tincore Keymapper to recognize my BT Shield controller.
However, I still haven't been able to get it to work like I want to... I can map the controller buttons and analog sticks, but they don't register in-game as 'screen touches' at all. A step in the right direction, yes, but still not a bonafide solution.
We can close this thread now, though, as my issue is now related directly with TKM and not custom kernels and SELinux.
**Edit: Update** Got Tincore Keymapper working, as was able to get my xbox controller recognized and buttons mapped and it's playable in CODM. Took quite a few steps to get it to work, but I finally figured it out.

Samsung note 10+ 5g not booting after firmware update

Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.

Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "

Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.

I didn't get any warnings at all. booted up fine.

Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too

I've tried all the posts but when I say start in odin, the phone restarts and gives an error

As you say you are super, my friend, I applied it step by step, the phone entered the download mode.

Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.

One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.

Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.

It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.

Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.

Question Reverting from GrapheneOS

I tried GrapheneOS and it's ok but too many compromises I have to make with several apps I'm using not working and small issues here and there.
Has anybody ever used Android Flash Tool to revert back from GrapheneOS to stock? If so, any issues?

Yeah plenty of times, no issues. Download firmware, extract it then flash-all in CMD

Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.

sabai27 said:
Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.
Click to expand...
Click to collapse
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge

I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?

Opensystem said:
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge
Click to expand...
Click to collapse
I would definitely love to see this with other manufacturers. I got a Windows ARM laptop that has become unresponsive in BIOS, meaning I can't tell the system to install a new Windows version via the Boot menu. Such a tool would save that device. It should be mandatory to offer decent web flashing tools.

asj0422 said:
I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?
Click to expand...
Click to collapse
Most things work with Sandboxed Google Play. But a few things don't like Android Auto, Google Pay and Chromecast. But other than that, I haven't had anything not work. They are close to getting Android Auto to work if I remember correctly - and Google Games ( I don't use either but looks like release is imminent). Check the other GrapheneOS threads on here or you can message me if you have any specific questions.
One thing I recommend though, is to leave "oem unlocking" enabled on the device after locking your bootloader. that way if something goes wrong, you can flash factory image. You don't want to brick your new phone. (I always leave my bootloader completely unlocked but that's a personal preference and I know the risks).

In other words, only a bunch of proprietary closed source gooble spyware crap doesn't work. The best thing about going to graphene or other security minded distributions of AOSP, is specifically *to* eradicate all of that.
It can be difficult initially, to clear yourself of all the gooble spyware, but its worth it and you don't even notice it after you get used to it. You're just much more safe and secure.

Question Random mac address on every reboot

Hello,
I have a problem with mac address on Oneplus 9 pro LE15BA OOS 11.2.10.10. Every time i reboot device i see slightly different mac address in settings even though i disabled mac randomization in wifi settings. Has anyone run into the same problem?

I just got a Oneplus 9 LE2115 and am seeing the same issue, my Unifi control panel is littered with mac addresses from the same phone (one for each reboot) even though i chose "Device MAC" for that SSID!
The problem is the Device MAC itself keeps changing.
So. Dumb.

.

You could log it as a fault on the OnePlus community forum, they'll ask you to supply logs.

Have anyone solve this problem？

dementate said:
I just got a Oneplus 9 LE2115 and am seeing the same issue, my Unifi control panel is littered with mac addresses from the same phone (one for each reboot) even though i chose "Device MAC" for that SSID!
The problem is the Device MAC itself keeps changing.
So. Dumb.
Click to expand...
Click to collapse
So glad I found this post! I have the same problem on my OP9 with Unifi, but it's infuriating me as I have MAC address filtration setup so it's breaking my wifi security situation. Has anyone else figured out how to solve this? If not, this phone is completely unusable on my home network. My 10 Pro does not have this issue.

centifanto said:
So glad I found this post! I have the same problem on my OP9 with Unifi, but it's infuriating me as I have MAC address filtration setup so it's breaking my wifi security situation. Has anyone else figured out how to solve this? If not, this phone is completely unusable on my home network. My 10 Pro does not have this issue.
Click to expand...
Click to collapse
It seems to be a bug specific to the op9 a12 update. One idea is to root your phone and force the MAC, at least until it's fixed properly

Appreciative said:
It seems to be a bug specific to the op9 a12 update. One idea is to root your phone and force the MAC, at least until it's fixed properly
Click to expand...
Click to collapse
Ah good to know, thanks for the reply. Did you read this in another post?
I am rooted, and have seen mention of using an Xposed module, but I'd rather not mess with that as I have had issues with it in the past and don't have a real need for any specific Xposed functionality.
Also have seen the following command
busybox config <net int> hw ether XX:XX:XX:YY:YY:YY, but unsure if this would be risky.
Any thoughts?
I'm wishing A13 would come out of beta....hopefully that'll fix it

centifanto said:
Ah good to know, thanks for the reply. Did you read this in another post?
I am rooted, and have seen mention of using an Xposed module, but I'd rather not mess with that as I have had issues with it in the past and don't have a real need for any specific Xposed functionality.
Also have seen the following command
busybox config <net int> hw ether XX:XX:XX:YY:YY:YY, but unsure if this would be risky.
Any thoughts?
I'm wishing A13 would come out of beta....hopefully that'll fix it
Click to expand...
Click to collapse
I haven't used macchanger in years but there used to be multiple versions in the play store. They all required root. They did all work at the time but this was pre-magisk. I haven't looked for a magisk module that may do the same. Or if termux (or termux+busybox) may support macchanger or setting device mac like you show in your example.
I read that this is a bug on OP9 a12 on reddit and also on xda. I also came across the following information in this thread:
[MOD][XPOSED][12-13] MACsposed - Restore support for setting custom MAC addresses on Android 12 and 13.
MACsposed Historically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed...
forum.xda-developers.com
MACsposed​Historically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed when the network state is altered. If you have encountered this problem, then you need MACsposed! MACsposed is an Xposed module that blocks the MAC address randomizer on Android 12 and 13 and allows you to once again make use of your favorite tools for setting your MAC address
Click to expand...
Click to collapse
I haven't tried it but I'm positive there is a way to achieve setting the Mac, whether xposed, magisk, or busybox/tools available, someone will have it available. Sorry I don't know more yet. Please report back what you find out, for others facing the same problem.
As for it being risky, write down your real MAC before you do anything for peace of mind. I hope there's a magisk module available, I don't particularly like using xposed for the same reason as you, had a few modules causing weird stuff to happen years ago and try to avoid it whenever possible

Goodluck.