I don't know what i did wrong. Every rom i tried which had already passed safety net wasn't passing safety net. Now i installed elixir A12 rom and the safety net is still not passing even after magisk hide.
I followed every step carefully. Installed magisk with patched boot.img method and still to no use.
Dont install magisk and it will pass.
k3lcior said:
Dont install magisk and it will pass.
Click to expand...
Click to collapse
its failing regardless of having magisk installed or not! idk whats wrong here. is it a boot file problem or what
Well i can guarantee you ArrowOS 11 and 12 passes safetynet without Magisk, dont know about Elixir.
PixelExperience and PixelExperience Plus pass safetynet without magisk. Dont know how with magisk because i dont use
k3lcior said:
Well i can guarantee you ArrowOS 11 and 12 passes safetynet without Magisk, dont know about Elixir.
Click to expand...
Click to collapse
tried arrowOS. i love pixel goodies. idk why i didnt like it. i'll try arrow12.
lsander said:
PixelExperience and PixelExperience Plus pass safetynet without magisk. Dont know how with magisk because i dont use
Click to expand...
Click to collapse
i'll check with them. whats the diffrence between PixelExperience/PixelExperience Plus?
the only reason i am using elixer is because of pixel android 12 goodies. but this safety net update keeps failing!
i even followed this video but to no use
I dont know what is the difference. I just saw that plus version has much more downloads so took this one. You can find in google the difference. I also wait for a12 but pixel experience rom. Dont like arrow.
From what i saw in arrow os rom a12 it passes safetynet without magisk and additional tweaks
If you have installed Magisk and safetynet does not pass the test, install Magisk modules: Riru and safetynet fix. Should help
Spoiler: Modules
use magisk alpha
download it from their telegram
Lu5ck said:
use magisk alpha
download it from their telegram
Click to expand...
Click to collapse
did it work for you?
tried every method i could read on prop's github and tried safety-net fix universal but i am unable to pass safety net on Android 12(elixir build).
the author says it passes by default but it does not! i don't think i have done any step wrong.
the procedure i followed is:
unlock bootloader on 12.5.5 official build.
root device with magisk and did magisk hide.(passes cts profile)
download elixer Android 12 zip.
install zip
format data+dalvik+cache
boot to rom.
download magisk
patch boot.img of elixir rom because the rom is not rooted!
boots into rom and do magisk hide
check safety net
basic integrity passes
cts profile match failed
not sure what i am doing rom???
saudahmedbass said:
tried every method i could read on prop's github and tried safety-net fix universal but i am unable to pass safety net on Android 12(elixir build).
the author says it passes by default but it does not! i don't think i have done any step wrong.
the procedure i followed is:
unlock bootloader on 12.5.5 official build.
root device with magisk and did magisk hide.(passes cts profile)
download elixer Android 12 zip.
install zip
format data+dalvik+cache
boot to rom.
download magisk
patch boot.img of elixir rom because the rom is not rooted!
boots into rom and do magisk hide
check safety net
basic integrity passes
cts profile match failed
not sure what i am doing rom???
Click to expand...
Click to collapse
Aythor said it passes by default because it is patched to pass without root. If you install magisk then it may not pass. Try to use clean rom without magisk and check if it passes.
saudahmedbass said:
did it work for you?
Click to expand...
Click to collapse
i am not using a12 but from what i saw in the telegram, others seem to report positively about it
furthermore, magisk alpha is many many commits ahead of the official v23
v23 pretty much is outdated
lsander said:
Aythor said it passes by default because it is patched to pass without root. If you install magisk then it may not pass. Try to use clean rom without magisk and check if it passes.
Click to expand...
Click to collapse
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
Lu5ck said:
i am not using a12 but from what i saw in the telegram, others seem to report positively about it
furthermore, magisk alpha is many many commits ahead of the official v23
v23 pretty much is outdated
Click to expand...
Click to collapse
true. i just read magisk canary documentationa and comments section of the blog post. it seems the magisk developer was hired by google to remove magisk hide from magisk-canary and the support on Android 12 won't have magisk hide but zygisk-module which is left as a tempelate for developers to create onto. this means safety-net will fail on Android 12
i know magisk v23 works on Android 12 but it will start failing once the vendors updates their apps!
saudahmedbass said:
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
true. i just read magisk canary documentationa and comments section of the blog post. it seems the magisk developer was hired by google to remove magisk hide from magisk-canary and the support on Android 12 won't have magisk hide but zygisk-module which is left as a tempelate for developers to create onto. this means safety-net will fail on Android 12
i know magisk v23 works on Android 12 but it will start failing once the vendors updates their apps!
Click to expand...
Click to collapse
Just try magisk alpha, not canary
Lu5ck said:
Just try magisk alpha, not canary
Click to expand...
Click to collapse
if i am not wrong canary / nightly / alpha / dev are the same? or if its not same can you link the download to alpha build?
saudahmedbass said:
if i am not wrong canary / nightly / alpha / dev are the same? or if its not same can you link the download to alpha build?
View attachment 5458809
Click to expand...
Click to collapse
Magisk Alpha is maintained by vvb2060, people who prefer magiskhide use it
Magisk Canary is basically the official test version without magiskhide, using the new zygisk denylist
Source code
GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
A Magic Mask to Alter Android System Systemless-ly - GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
github.com
Release
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
saudahmedbass said:
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
Click to expand...
Click to collapse
I told you this in a second post..
Lu5ck said:
Magisk Alpha is maintained by vvb2060, people who prefer magiskhide use it
Magisk Canary is basically the official test version without magiskhide, using the new zygisk denylist
Source code
GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
A Magic Mask to Alter Android System Systemless-ly - GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
github.com
Release
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
Click to expand...
Click to collapse
i will need the apk unfortunately. i am unable to access telegram in my country due to ban! (
saudahmedbass said:
i will need the apk unfortunately. i am unable to access telegram in my country due to ban! (
Click to expand...
Click to collapse
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Related
Hey,
Does anyone have or can make a November patched boot image that has just the unlocked state check disabled so SafetyNet will pass? I want to play PoGo and have no use for root or Magisk at this time, but can't play because Niantic added extra checks beyond just SafetyNet passing. The Canary build of Magisk is unstable right now and among other things blocks charging with the device off, which is kind of dangerous. The Magisk hide on Pixel 3s also still seems hit or miss from that build. I also don't want to have to wipe my phone just to get rid of Magisk and pass SafetyNet right now.
I don't have my Linux dev environment up to date because I haven't done kernel work in a couple years, so hopefully someone else is already set up to throw in the couple quick patches from source and spit out an image.
Thanks!
Why are you looking at the Magisk Canary build? 17.3 Beta is working just fine on both Pixel 3 and PIxel 3 XL.
sliding_billy said:
Why are you looking at the Magisk Canary build? 17.3 Beta is working just fine on both Pixel 3 and PIxel 3 XL.
Click to expand...
Click to collapse
Hiding the Magisk Manager app itself (which PoGo looks for) doesn't work correctly. It sometimes creates a second copy and also can cause root to be lost.
elkay said:
Hiding the Magisk Manager app itself (which PoGo looks for) doesn't work correctly. It sometimes creates a second copy and also can cause root to be lost.
Click to expand...
Click to collapse
Gotcha. I've never lost root with 17.3, nor has anything failed due to Manager not hiding or creating a duplicate. Stinks that they are that concerned about device rooting for a game.
Hello all,
This is FYI.
As the title says, I am on RUI latest version with Magisk safetynet passing even with EdXposed installed (Gravitybox and some other modules works without any issue).
SELinux mode set to Enforcing for all these apps to work (Usually Magisk safetynet fails when SElinux is set to enforcing but found a workaround by internet research).
Safetynet pass means all payment apps work.
Viper4Android works fine.
Can edit system (xml) files in RUI with root browser.
Attached picture
View attachment 5121221
Thank you
Hey bro ,Dolbyatmos Viper works on realmeui C07, do you need my help?
Cancer..93 said:
Hey bro ,Dolbyatmos Viper works on realmeui C07, do you need my help?
Click to expand...
Click to collapse
Frankly speaking, I didn't find a working Dolby version for realme 5 Pro.
Please make a new thread, I would appreciate that. Also magisk should pass safetynet.
Thanks.
Alright. But how? I just reverted from A11 custom rom to stock with only twrp and modified vbmeta installed but already at start safetynet fails.
I want to install custom ROM but I only have one phone right now, I use this X3 Pro for several apps(mostly banking, internet food services, delivery services) that requires SafetyNet.
Read the ROM description and look for safety net, if it's not written then just ask if it supports it. If you've still got no luck, backup your stock system (full twrp backup) and then flash the ROM and test if it supports safety net
ArrowOS 11/12, Pixel Experience.. these im sure of.
CrDroid
PhotonIce said:
Read the ROM description and look for safety net, if it's not written then just ask if it supports it. If you've still got no luck, backup your stock system (full twrp backup) and then flash the ROM and test if it supports safety net
Click to expand...
Click to collapse
yeah... so many questions can be avoid by just reading threads or google it...
Almost all ROMs except for LineageOS.
You can pass SafetyNet with LineageOS.
Just install Magisk, enable MagiskHide, and properly setup "MagiskHide Props Config" module.
komodo os
plskillme said:
I want to install custom ROM but I only have one phone right now, I use this X3 Pro for several apps(mostly banking, internet food services, delivery services) that requires SafetyNet.
Click to expand...
Click to collapse
All of the rom I tried are passing. If it doesn't just install MagiskHide Props Config. Steps are here. If you are using magisk v23 then enable magisk hide. If you using magiskv24 then enable zygisk, enforce list and choose google play service in the deny list then tick com.android.gms and com.android.gms.unstable. If you can't find it then tick show os app in the menu then reboot. It should pass.
tazaga said:
komodo os
Click to expand...
Click to collapse
this thing doesn't exist
gringo80 said:
this thing doesn't exist
Click to expand...
Click to collapse
There is this ROM but just didn't post on xda. Idk why dev don't post it but you can search on Google and go to their source forge folder. You can download there.
Alec Chan said:
There is this ROM but just didn't post on xda. Idk why dev don't post it but you can search on Google and go to their source forge folder. You can download there.
Click to expand...
Click to collapse
rom post in xda need to provide their kernel source code which is something for whatever reason some people find it uncomfortable to do so
zinconnu said:
You can pass SafetyNet with LineageOS.
Just install Magisk, enable MagiskHide, and properly setup "MagiskHide Props Config" module.
Click to expand...
Click to collapse
Actually, some LOS contributors put together a safetynet fix without the need of magisk, obviously not an official thingy.
GitHub - luk1337/ih8sn
Contribute to luk1337/ih8sn development by creating an account on GitHub.
github.com
SafetyNet seems to pass out of the box with most of the ROM's now, unless you flash Magisk.
But the latest version (Magisk 24.1) with zygisk, has a module available called Universal SafetyNet Fixer (by kdrag0n) which seems to fix both CTS Profile and Basic integrity.
Edit:
The USNF module moded by displax fixes both safetynet and security patch info! Thank
rocketda7331 for your experience and nice guidance!
Also, thank BillGoss for your fast help!
Your info gave me the chance to turn back from my wrong direction!
As shown here [ https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh ], they only have OOS [11] device fingerprints:
OnePlus 8T China KB2000 (11):OnePlus:KB2000=OnePlus/OnePlus8T_CH/OnePlus8T:11/RP1A.201005.001/2108261338:user/release-keys__2021-08-01
OnePlus 8T India KB2001 (11):OnePlus:KB2001=OnePlus/OnePlus8T_IND/OnePlus8T:11/RP1A.201005.001/2110091916:user/release-keys__2021-10-01
OnePlus 8T Europe KB2003 (11):OnePlus:KB2003=OnePlus/OnePlus8T_EEA/OnePlus8T:11/RP1A.201005.001/2110091916:user/release-keys__2021-10-01
OnePlus 8T Global KB2005 (11):OnePlus:KB2005=OnePlus/OnePlus8T/OnePlus8T:11/RP1A.201005.001/2110091917:user/release-keys__2021-10-01
OnePlus 8T T-Mobile KB2007 (11):OnePlus:KB2007=OnePlus/OnePlus8TTMO/OnePlus8TTMO:11/RP1A.201005.001/2108091917:user/release-keys__2021-08-01
But I'm already on LineagsOS 19.1 (Android 12), and I forgotttttttttttt to check the fingerprint of OOS 12 by myself before installing LOS...
Although OOS 11 fingerprint is still able to pass SafetyNet, but it also gives me a "Platform: Out of date" false alarm under "Android security patches" even with latest LOS build installed.
Does any gentleman happens to have OOS [12] device fingerprints for kb2005 or kb2007?
Thanks in advance!!!
ro.build.display.ota: KB2005_11_C.35
ro.build.fingerprint: OnePlus/OnePlus8T/OnePlus8T:12/RKQ1.211119.001/R.202208261328:user/release-keys
If you want other properties, let me know.
BillGoss said:
ro.build.display.ota: KB2005_11_C.35
ro.build.fingerprint: OnePlus/OnePlus8T/OnePlus8T:12/RKQ1.211119.001/R.202208261328:user/release-keys
If you want other properties, let me know.
Click to expand...
Click to collapse
Thanks a lot! You're GREAT!
Sadly this fingerprint can not pass SafetyNet, it gives a "CTS profile match: Fail".
But it fixes the "Platform: Out of date" in "Android security patches"!
You still saved my day! Thank you for your selfless help!
By the way, the LOS 19.1 (20221013) fingerprint is:
OnePlus/OnePlus8T/OnePlus8T:12/RKQ1.211119.001/R.20220730031:user/release-keys
which looks very similar to the OOS C.35 12 fingerprint.
Hmm... Maybe OnePlus just forgot to update it's SafetyNet status?
Found a related issue:
SafetyNet fails on C.20 update for OnePlus 8 Pro · Issue #188 · kdrag0n/safetynet-fix
The "C.20" update for OnePlus 8 Pro based on Android 12 and the OxygenOS 12.1 overlay in correlation with "SafetyNet-Fix v2.2.1" completely blocks the fingerprint scanner. Uninstalling this module ...
github.com
Issue is still open, seems OnePlus has broken something...
GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
rocketda7331 said:
GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Click to expand...
Click to collapse
Yeah thx I already have that.
With that and hideprops module installed, I can already pass safetynet with OOS 11 fingerprint.
But it's android 11 fingerprint and I'm running android 12 (lineageos 19.1), so using that fingerprint gives me "Platform: Out of date" in "Android security patches".
And as shown above, OOS 12 fingerprint seems problematic too.
For now I can only switch back to OOS 11 fingerprint and watch how this will end...
What are you trying to achieve? If you just want to pass safetynet, you can ditch magiskhideprops module. safetytnet fix module will only spoof your fingerprint for google play services, elsewhere you will have correct fingerprint. I am also on LOS19.1 and everything is reported up to date in Android security patches with this setup. If you wish to keep using magiskhide props for other purposes, you can keep it, but reset your fingerprint.
I will also point out that the linked safetynetfix is modded by displax and is not the original you might have if you installed it ages ago. To pass safetynet nowadays you should update it to this one.
rocketda7331 said:
What are you trying to achieve? If you just want to pass safetynet, you can ditch magiskhideprops module. safetytnet fix module will only spoof your fingerprint for google play services, elsewhere you will have correct fingerprint. I am also on LOS19.1 and everything is reported up to date in Android security patches with this setup. If you wish to keep using magiskhide props for other purposes, you can keep it, but reset your fingerprint.
Click to expand...
Click to collapse
I tried to pass safetynet with a fingerprint from oos 12, not oos 11.
Safetynetfix module is not enough for me because my other apps and games also checks safetynet, so I also have hidepropsconfig module installed. And I use YASNAC to check safetynet.
With hideprops module enabled and oos 11 fingerprint spoofed, I can pass safetynet check, but also got "Platform: Out of date".
With hideprops module enabled and oos 12 fingerprint spoofed, I cannot pass safetynet check, but the platform became okay.
With hideprops module disabled, I cannot pass safetynet check with YASNAC (but google play is okay because safetynetfix module is active), and the platform is okay too. Is this your current state?
IAAxl said:
I tried to pass safetynet with a fingerprint from oos 12, not oos 11.
Safetynetfix module is not enough for me because my other apps and games also checks safetynet, so I also have hidepropsconfig module installed. And I use YASNAC to check safetynet.
With hideprops module enabled and oos 11 fingerprint spoofed, I can pass safetynet check, but also got "Platform: Out of date".
With hideprops module enabled and oos 12 fingerprint spoofed, I cannot pass safetynet check, but the platform became okay.
With hideprops module not enabled, I cannot pass safetynet check, and the platform is okay too. Is this your current state?
Click to expand...
Click to collapse
Are you sure you are using modded safetynetfix module by displax? See if it says "modded by displax" in your magisk modules section. If you have confirmed this, disable magiskhideprops and reboot your phone. Clear data/cache for google play services(note, this will reset your google related settings) and run safetynet attestation. It should pass this way. Apps check safetynet through google, they aren't running their own checks for that, however they can detect root through other methods that don't care about your safetynet status. What app do you have problem with, I could try. You don't have to mess with fingerprints with this module and I assume this is what is actually messing things up for you.
I have oneplus 8t, running lineageos 19.1 and only with safetynetfix mod I can pass safetynet everywhere every time.
rocketda7331 said:
Are you sure you are using modded safetynetfix module by displax? See if it says "modded by displax" in your magisk modules section. If you have confirmed this, disable magiskhideprops and reboot your phone. Clear data/cache for google play services(note, this will reset your google related settings) and run safetynet attestation. It should pass this way. Apps check safetynet through google, they aren't running their own checks for that, however they can detect root through other methods that don't care about your safetynet status. What app do you have problem with, I could try. You don't have to mess with fingerprints with this module and I assume this is what is actually messing things up for you.
I have oneplus 8t, running lineageos 19.1 and only with safetynetfix mod I can pass safetynet everywhere every time.
Click to expand...
Click to collapse
I'm using kdrag0n's universal safetynet fix module v2.3.1, with propsconfig by Didgeridoohan.
I'll check displax's modded version and try your build!
Thanks a lot for sharing your success experience!
IAAxl said:
I'm using kdrag0n's universal safetynet fix module v2.3.1, with propsconfig by Didgeridoohan.
I'll check displax's modded version and try your build!
Thanks a lot for sharing your success experience!
Click to expand...
Click to collapse
Disable propsconfig. Displax' modded version will be all you need to pass safetynet and you will have correct fingerprint(so correct security updates information as well) everywhere else.
rocketda7331 said:
Disable propsconfig. Displax' modded version will be all you need to pass safetynet and you will have correct fingerprint(so correct security updates information as well) everywhere else.
Click to expand...
Click to collapse
It worked!
Thank you so much for your experience and nice guidance!
You saved my year!
IAAxl said:
It worked!
Thank you so much for your experience and nice guidance!
You saved my year!
Click to expand...
Click to collapse
Also check article
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Hi!
I just updated to latest Canary of Magisk(25210) and I just noticed AdAway stopped working. it says to reinstall the systems hosts file. when I make the attempt it fails silently.
is this happening to anyone else or is it just me?
Nope, not just you....I saw some bug posts in github so suspect there is a bug. I think you can wait for an update or possibly downgrade to 209. I think Ima just gonna wait a bit.
ok thanks! I'll wait as well.
DevilDaHusky said:
Hi!
I just updated to latest Canary of Magisk(25210) and I just noticed AdAway stopped working. it says to reinstall the systems hosts file. when I make the attempt it fails silently.
is this happening to anyone else or is it just me?
Click to expand...
Click to collapse
As cmh714 said...
Also, 25206 seems to be the last canary build without a "bug".
EDIT: I think 25209 may be ok.
25210 breaks module loading · Issue #6688 · topjohnwu/Magisk
Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...
github.com
Lughnasadh said:
As cmh714 said...
Also, 25206 seems to be the last canary build without a "bug".
25210 breaks module loading · Issue #6688 · topjohnwu/Magisk
Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...
github.com
Click to expand...
Click to collapse
thanks for the tip! I just so happen to have 25206 in my phone so I'll be reinstalling it.
edit: well nevermind that didn't work. it just autodownloaded the latest canary.
I'm using Magisk 25200 with zero issues🫠
25209 has no issues AFAIK
gpvecchi said:
25209 has no issues AFAIK
Click to expand...
Click to collapse
Worked perfectly for me until I updated
25208 works, too.
So I uninstalled 25210 apk. Installed 25208 apk downloaded previously. Opened Magisk 25208 and direct installed. Reboot.
Do not update the Magisk app until 25211 is released.
From Magiskokoro on the Telegram channel for Magisk:
"For anyone use official Canary Magisk, don't update to Magisk 25210, the module functions might not work.
Magisk Delta users won't be affect"
MArtyChubbs said:
25208 works, too.
So I uninstalled 25210 apk. Installed 25208 apk downloaded previously. Opened Magisk 25208 and direct installed. Reboot.
Do not update the Magisk app until 25211 is released.
Click to expand...
Click to collapse
25208 has issue hiding app.
How can I get 25209? Where do I get the older releases?
rester555 said:
How can I get 25209? Where do I get the older releases?
Click to expand...
Click to collapse
I think it is possible to find in the magisk-files repo,
Update Canary Channel: Upstream to 2717feac · topjohnwu/[email protected]
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
i think this link is the 25209 apk: https://cdn.jsdelivr.net/gh/topjohn...8e568f9cc101eaf64bb5d9edb8a34/app-release.apk
larenhot said:
I think it is possible to find in the magisk-files repo,
Update Canary Channel: Upstream to 2717feac · topjohnwu/[email protected]
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
i think this link is the 25209 apk: https://cdn.jsdelivr.net/gh/topjohn...8e568f9cc101eaf64bb5d9edb8a34/app-release.apk
Click to expand...
Click to collapse
It keeps forcing me to update the app to 25210
rester555 said:
It keeps forcing me to update the app to 25210
Click to expand...
Click to collapse
How is it actually forcing you? I've always seen it just prompting you to update app/magisk.
krakout said:
How is it actually forcing you? I've always seen it just prompting you to update app/magisk.
Click to expand...
Click to collapse
I ended up uninstalling the whole thing. I deprecated to 25206 and 25209... After installing both of those, I am still having an issue with systemless hosts installing and AdAway playing nice. I still get the error
Same issue but I am waiting for an official magisk update. Maybe today or tomorrow...
I wonder if this persists with a removal of -w with a new image. I would hate to have to wipe the whole phone to fix this issue.
rester555 said:
I wonder if this persists with a removal of -w with a new image. I would hate to have to wipe the whole phone to fix this issue.
Click to expand...
Click to collapse
This is a Magisk issue and not an Android 13 issue. So, you wouldn't need to wipe your phone if you had upgraded your Magisk app and flashed the updated, patched init_boot file. You will just need to upgrade the Magisk app to the 25211 build, patch another stock init_boot.img and flash that newly patched init_boot.img.
If you check on the Magisk GitHub page, the error was pointed out and resolved. In one of the changes, a programmer set the command to make a directory AFTER a command that makes that location privatized (and thus, the directory cannot be created). It was supposed to be the other way around.
NippleSauce said:
This is a Magisk issue and not an Android 13 issue. So, you wouldn't need to wipe your phone if you had upgraded your Magisk app and flashed the updated, patched init_boot file. You will just need to upgrade the Magisk app to the 25211 build, patch another stock init_boot.img and flash that newly patched init_boot.img.
If you check on the Magisk GitHub page, the error was pointed out and resolved. In one of the changes, a programmer set the command to make a directory AFTER a command that makes that location privatized (and thus, the directory cannot be created). It was supposed to be the other way around.
Click to expand...
Click to collapse
I understand this... I don't see 25211.