yashsingh1/xdaforums huggingface dataset:
[Magisk] Lughnasadh:
The repo was removed from Magisk. You can use this instead...

Release Release 0.2.2 · Fox2Code/FoxMagiskModuleManager

Add app backup support files (Note: Only allow to backup the app, not the modules) Improve code-base for translators Add Japanese translations by @lindwurm Update android gradle plugin

github.com
[Magisk] awakener777:
Oh that's fantastic! Thank you so much. Made my day
[Magisk] pndwal:
Sorry, I'm not clear what you've done.

Did you originally have setup as above? Then bootlooped on updating app??? - This would seem strange.... or did it bootloop / brick at a later stage?...

Normally, just take update for App (it's not hidden according to your info and this is best for updates), then take Direct Install to update Magisk (mask) itself. PW
[Magisk] TanakaX5:
Hey,

Thanks for your reply.

I Updated, then root Was gone and I think I, can't remember exactly, flashed the boot Image again as per "select a file"

After that my 8t bootlooped.

I did a factory reset and then it was completely fxxx uped, no Radio etc.

So this time I make sure I select the recommended option.

BTW I never hide the app, no problems at all till now.

Greets

T
[Magisk] pndwal:
Seems you're unclear on what you did also, and if bootlooped on updating App or Magisk itself, etc. 😬

Assuming you have root restored as per details given, updates to Magisk should work fine using Direct install method I mentioned.

If you ever take an OTA firmware update, you need to Uninstall Magisk (not the App; use big red button in App home screen) first. Use Restore Images; no need for Complete Uninstall. After OTA do initial installation again, ie. Download complete ROM corresponding to OTA, extract boot image, use Select and Patch a File selecting new image, flash patched image using Fastboot...

Nb, Magisk modules / settings are preserved with this method, and modules can potentially cause bootloops if not compatible with updated OS. Consider disabling any that may cause issues before taking Uninstall Magisk for OTA... PW
[Magisk] nowster:
A Pixel 3a which was passing SafetyNet fine a day or two ago is failing basicIntegrity as of this morning. (Magisk Stable 21, plus SafetyNetFix 2.1.2, plus RiRu/LSPosed/XPrivacyLua)
[Magisk] nowster:
Looks like a false alarm. I suspect a mix-up between boot images.
[Magisk] replica9000:
I actually didn't realize I needed to toggle that every time I opened the app.
[Magisk] replica9000:
I'm on the US ROM. It seems really hit or miss, but there's a higher chance of success with the EU ROM. It's not important enough to wipe my phone to try though.
[Magisk] pndwal:
But once Netflix is in list, it should show without selecting Show system apps. System apps show this way for me...

Yeah, saw that with OnePlus; that's why I asked... Some had success just by using fingerprint from EU OP ROM, which may be all you need; some didn't. You could try other fingerprints simply by installing MagiskHide Props Config module and configure using a terminal emulator ('type props')...

@BillGoss, could you say which ROM variant (region) you have on OP8T? PW
[Magisk] Qnorsten:
I have the same device and I just always do these steps

Download full OTA zip, most often using oxygen updater app so I can get it quicker.

Install OTA update by local update function

Before reboot go into magisk app and pick Install to inactive Slot.

And everything works great. Only time I had a bootloop it was caused by a substatum theme i had installed.
[Magisk] TanakaX5:
Thnaks mate,

Thanks mate,

But my question was just about updating the magisk app, not a OTA.

Thanks anyway
[Magisk] Qnorsten:
Oh in that case i just update the magisk app and then do a direct install.
[Magisk] TanakaX5:
Tight, will try
[Magisk] BillGoss:
My OP 8T is KB2000 DDR5 and I'm on 11.0.11.11.KB05AA
[Magisk] replica9000:
My 8T has LPDDR4X
[Magisk] pndwal:
A Late Announcement re. end of SafetyNet API, and an alert to possible needed efforts to pass new Play Integrity API checks:

Google Play Integrity API is to replace Google's SafetyNet Attestation API.

This news is actually old, having been announced about a month ago in a newsletter:

https://newsletterest.com/message/7...w-games-resources-Play-Integrity-API-and-more

This API will return / include device status results:

- MEETS_BASIC_INTEGRITY

- MEETS_DEVICE_INTEGRITY

- MEETS_STRONG_INTEGRITY

Overview:

https://developer.android.com/google/play/integrity

Documentation:

https://developer.android.com/google/play/integrity/overview

Old SafetyNet API Doc:

https://developer.android.google.cn/training/safetynet/attestation.html

I have no idea if this change is designed to coincide in any way, or even if it might or can, with Shawn's predicted change here:

www.twitter.com/shawnwillden/status/1463518016214163456?t=LdgNHLOicVYviPRjXet4Jw&s=19

Time will tell whether the new API will be able to be bypassed by triggering fallbacks to non-hardware backed attestation methods as the old one was or by other means for any additional limited time until 'OEMs fix their hardware attestation'...

👀 😬 PW
[Magisk] shoey63:
So down the track it will be potentially impossible to hide unlocked bootloader and or root on hardware backed attestation devices?
[Magisk] zzz2002:
A whisper on the wind - devices without hw attestation may be barred/dropped/unsupported by big G in the future. G new OS fuchsia!
[Magisk] pndwal:
Well G has required that devices ship with hardware-level key attestation since Android 7.0 (API level 24) with a root certificate signed with Google's attestation root key to ship Play Services...

Where things get murky is when keys in the certificate chain have been revoked. "Unless all are valid and the root is the Google root key mentioned above, you shouldn't fully trust the attestation".

Also "Devices containing revoked certificates are still at least as trustworthy as devices that only support software attestation."

https://developer.android.com/training/articles/security-key-attestation PW
[Magisk] pndwal:
Not just potentially, it's a fait accompli... PW
[Magisk] HippoMan:
All the more reason for me to remain with my increasingly outdated OP 7Pro running Android 10 and the now ancient Stable 23.0 Magisk. So far, I have not hit any roadblocks with that regarding SafetyNet nor root.

Although I wouldn't be surprised if Google's accompli will eventually seal my fate with even this configuration.

<pipe-dream>I wish I was as rich as Elon Musk (or even 1% as rich). I'd then develop and market an alternative to Android devices and a variant of the Android OS which allows us to run our apps the way we want without being hobbled by SafetyNet-like features.</pipe-dream>
[Magisk] pogo-airsupport:
What I foresee happening, is developers will have to justify why they are making these calls to verify integrity, AND per documentation, 10000 calls per day per developer.

Google will probably use this to restrict what apps can request verification. For example, bootloader unlock shouldn't affect certain apps, so they can't request the highest level of integrity, etc.
[Magisk] pndwal:
The thinking:

www.twitter.com/shawnwillden/status/1471240680206860288?t=rWxHLyO_0z6TELWibsaeGw&s=19

The clarity / quandary, even from / for Google!:

www.twitter.com/shawnwillden/status/1471240812411244544?t=mBxcyGOEttaV1v1z11mtOA&s=19

Macca's anyone?... 😬 PW
[Magisk] pogo-airsupport:
Well I mean it's quite easy to fix. You have to apply to use the API. Meaning, it's going to need to meet a certain bar. For example, bank apps should have more security than games. And so you give them 3 tiers to apply for, and criteria to qualify for each. For example, games shouldn't need to know if you have unlocked bootloader, where as banking apps might
[Magisk] sieger007:
Xiaomi aka mi stock apps unaffected by Magiskhide

this applies to any stock Mi ROM

there are certain Mi apps that remain permanently unchecked against magiskhide options. the most notorious is the securitycenter app which runs as a common app ID ( = shares common app ID. I have actually e found that it it has spyware Incorporated in it and therefore the entire basis of the ROM becomes untrustworthy take a look at the screenshot.

)

you can check them but after closing magisk and relaunching it they will end up being unchecked.

why does this happen?

where does magisk store its magiskhide entries? is it possible to manually edit the file like a config file or a SQL lite file

take a look at the screenshot

also it would help to know if it is possible to run a stock ROM without this security center app or some work around.
[Magisk] pndwal:
If you type 'magisk --denylist' in a Terminal Emulator you should see what you need:

"DenyList Config CLI

Usage: magisk --denylist [action [arguments...] ]

(or Usage: magisk --hidelist [action [arguments...] ] ? Just type magisk to check option 👍)

Actions:

status Return the enforcement status

enable Enable denylist enforcement

disable Disable denylist enforcement

add PKG [PROC] Add a new target to the denylist

rm PKG [PROC] Remove target(s) from the denylist

ls Print the current denylist

exec CMDs... Execute commands in isolated mount

namespace and do all unmounts

I believe add PKG works for MIUI securitycentre. PW
[Magisk] pndwal:
I don't see this. 🤔

Seems Dev can still simply generate an API key as with old SafetyNet API and get default quota allotment (per project) of 10,000 requests per day for API calls...

For the current API it seems Dev can simply generate an API key using Create credentials button or by selecting an API key already associated with the project that has enabled Android Device Verification API, and will receive the default quota allotment (per project) of 10,000 requests per day for API calls. Seems only if "your app requires an increased quota" a Dev must make a request before deployment.

The only real change I can see here is that API calls may no longer be throttled to 5 per minute!

But the tiers needing requesting only relate to call quota, not attestations returned! Indications are that all attestations may be available...

And there's only two tiers mentioned for this, Standard and Raised!

Is this wishful thinking? 😜 PW
[Magisk] pndwal:
Bit further on imminent SafetyNet replacement, new Play Integrity API:

https://developer.android.com/google/play/integrity/setup#configure-api-responses

Detail:

https://developer.android.com/google/play/integrity/verdict

There are also many possible Error codes. See here:

https://developer.android.com/google/play/integrity/error-codes

PW
[Magisk] pndwal:
Some Relavent Notes applicable to current status of:

- Magisk Module Repo

- SafetyNet Check

- MagiskHide

From Alpha Magisk Telegram group Admin.

Translated from Chinese.

(Have fun with interpretation!):

https://t.me/magiskalpha/397

Clarification on comments about compatibility above.

From another Alpha Magisk Telegram group Admin.

Message 'forwarded from Shana'.

Translated from Chinese.

https://t.me/c/1414270883/29497

👀 PW
[Magisk] Renate:
The documentation in the Developer's Guide seems a bit ambiguous to me. If I have this correct is the logic for files in the overlay.d directory in the ramdisk as so?

if (file_is_an_rc)
{
inject_the_file_into_init_input
}
else
{
if (file_already_exists)
{
replace_file
}
else; // do nothing
}

This means that there is no way to get rid of things like init.usb.rc, init.usb.configfs.rc with an empty file.

Would it be possible to make the logic like this instead?

if (file_already_exists)
{
replace_file
}
else
{
if (file_is_an_rc)
{
inject_the_file_into_init_input
}
else; // do nothing
}

Or is the problem that by the time the overlay.d gets processed all the normal rc's have already been digested?
[Magisk] moocow1452:
Checking in, since somebody blabbed and posted ChinaLinda's method to get Root on the Go to XDA News, so we're famous. Could we use that method to get Magisk installed, either through harvesting the su binary and putting it in, or use SuperSU's access to clear the way for Magisk's installation? It seems to reject changes to boot out of hand, so I'm wondering if there is a way to turn that off.
[Magisk] pndwal:
USNF fix for Realme devices coming any tick of the clock!

https://github.com/kdrag0n/safetynet-fix/pull/129

Thanks to @osm0sis / testers...

https://github.com/kdrag0n/safetynet-fix/issues/115#issuecomment-998340161

(User-patched USNF 2 posts up)

👀 PW
[Magisk] traversone:
any idea about this issue with Android Box (PIE) and Zygisk enabled: the Shamiko module seems to be correctly installed but it fails with "post-fs-dat.sh fails to run, Magisk is broken..etc..etc..." ?

thank you
[Magisk] MartK87:
Got an issue I can't seem to get round.

Device Galaxy S5 (SM-G900I)

TWRP - Latest

Magisk v23 ZIP & APK

I cannot get Magisk to work properly. According to Root Check the device is rooted but on Magisk I lose the 4 options you get along the bottom of the screen. So I cannot access module options. Ramdisk shows as 'Yes' but I get 'Installed: N/A' it seems its not properly installed. I have done numerous stock ROM reflashes and still no luck.

Am I missing something?

Thanks.

Just an update: Got the .TAR file of stock image patched successfully using Magisk. Reflashed the newly patched .TAR file. Opened up Magisk which is still exactly the same as before. Flashed Magisk v23.zip in TWRP and Magisk still remains the same with no module options.

Any ideas?
[Magisk] zgfg:
Were you updating Magisk from an older version?

And with that older version, you had your Magisk app/mngr (now it's called Magisk App, since v21.x it was called Magisk Manager) hidden (repackaged/renamed), and you didn't restore or delete before updating Magisk?
[Magisk] MartK87:
Thanks for getting back

I did it all completely from scratch. I put a fresh stock ROM on then worked with just Magisk ver 23 for both the ZIP and APK. Every time I try a different version of Magisk I am reloading the Stock ROM and doing a data / cache wipe just to make sure everything is completely refreshed before putting different versions of magisk on. I know its a long way round it but it at least reassures me haha

Problem is though, with earlier versions of magisk (22 and below) when i go into modules and click 'Install from storage' it says no applications installed to handle it. That is very strange because I don't get that on my S8 but I need to be able to add modules from storage.

In a real pickle here

Thanks for getting back
[Magisk] pndwal:
Which ROM / Android version? PW
[Magisk] MartK87:
I believe it is version 6 which i Kitkat is that right? Thats the latest available version for my S5. It is the Telstra ROM. Its definitely a Telstra phone even though its unlocked it came with the Telstra Bloatware. So I get the latets Stock ROM from Sammobile which I think is Nov 2017 is the absolute latest. Rom name: SM-G900I_1_20171122095253_6llh26rhew_fac_G900IDVU1CQD1_G900ITEL1CQD1_G900IDVU1CQD1_G900IDVU1CQD1_TEL

I did have Magisk working on here before though. I have had to factory reset it and put a new stock on because I kept getting an error message saying 'Play service has stopped working; It wouldnt go away even from a factory reset so I have had to resort to a fresh stock ROM. I just cannot get Magisk working though :(

Just to also add, If I try an earlier version of Magisk (Before 22) Yes, it works and I get those 4 options back but I just cannot install modules from storage. It keeps opening up Drop box. I will then disable Drop Box and it informs me there is no application installed to handle it.

Very frustrating seeing as Magisk was actually working on here before.
[Magisk] zgfg:
Android 6 is not KitKat but Marshmallow

Check on Github if Magisk you are trying to install supports Android 6; or KitKat = A 4.4 - whichever you really have
[Magisk] MartK87:
Yep it sure does. Supports android 5 and higher and I am definitely on Android 6.
[Magisk] pndwal:
Seems it's A6, Marshmallow... About Phone should confirm...

Should be compatible... Can't you install older Magisk, then take update using Direct install? PW
[Magisk] zgfg:
Then again, when you are on that Magisk v22, how is your Magisk app/mngr called?

Magisk Manager/Magisk App or something renamed?

If you go to its Settings and scroll down, do you have an option:

Restore Magisk Manager (Magisk App)?
[Magisk] MartK87:
I don't have v22 installed. I have 23 at the moment. My Magisk Manager name is called 'Magisk' on the app drawer.

In settings I have VERY limtied settings. I just have Themes, Language, Update Channel, DNR over HTTPS, Check updates, Download path and thats it.

Is it possible the bootloader is locked and if so how do I find out if its locked?

Looks like someone else had similar problems also unable to resolve it

https://www.reddit.com/r/Magisk/comments/o3s7kv
[Magisk] zgfg:
My question was when you reinstalled v22 and you said Mgisk was 'working' then - then how the app was called and then in Settings do you have Restore Mgisk Mngr/App option

Or going the other side - now when you are on 'non-working' Magisk v23, go to Settings, Apps or Apps drawer, do you see more than one Magisk Mngr/App (even under a different name)

Why all that: Every few days somebody reports the same problem like you. And for 99% of them the cause is very simple: they left hidden/renaned/repackged old Magisk mngr/app before updating Magisk
[Magisk] pndwal:
Actually, looks like you may have this long-running Magisk issue with Android 6, 7 on armeabi-v7a devices:

https://github.com/topjohnwu/Magisk/issues/4174

Looks like Canyie is back on the job recently, so you may see a solution soon... There are test builds / notes here that may help you meanwhile...

Confirmation affects S5:

https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-866326377

Workaround: seems you may be able to keep V23.0 Magisk (mask), uninstall App and install old Manager 8.0.7 (Seems this may be a regression in the app only):

https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-954061584

👀 PW
[Magisk] MartK87:
Hi there. I have never had Magisk working with v22. Magisk worked for me for many years on this S5. I had many errors coming up informing me 'Google play services have stopped working' I could not egt rid of these errors. A factory reset didn't get rid of them.

I ended up flashing a fresh Stock ROM. after I flashed it I wanted to root it again with Magisk. I cannot do this with any versions above v20. Any version above V20 I get no options for Modules.

Any version below v20, yes it works bur whenever I try to install a module from storage it says there is no application to handle the opening of the storage.

So which ever version I try now of Magisk, it does not work. There is always a new problem.

I wondered if it is maybe the bootloader but I think I saw somewhere someone said there is no bootloader for the S5.

If I were to try another version of Magisk I would do this.

I would TWRP Wipe System, Data, Dalvik Cache and cache.

I would then pull the battery out.

Put battery in andp ut it into download mode.

I would then reflash Stock ROM again and let it bring me to setup splash screen. After that I would do a factory wipe and boot it up completely. I would then try a new version of magisk.

I apply the exact same procedure mentioned above every time I try a new Magisk Version.

I have followed these guides exactly:

Installation

The Magic Mask for Android

topjohnwu.github.io

How to Install Magisk on your Android Phone

Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!

www.xda-developers.com

Still no luck. Close to throwing phone in bin unless anyone wants to buy it?

Thanks for reply.
[Magisk] MartK87:
Thanks for getting back. This is very interesting. Glad to know I am not the only one with the problem. I have been doing this non stop for 7 and a half hours today anf got nowhere.

The wierd thing is... Magisk was working totally fine on my phone for about 3 years but I forgot which version I had. Would love to know someone else with an S5 with a working version of Magisk. Not too worried about it being a new version I just want it working. I also just want to be able to press 'Install module from local' instead of it keep telling me no applications can handle it.

I am gutted I didn't mark down the version I had of magisk which worked for me for all those years.

Thanks everyone for your help and will always welcome more ideas if anyone got any?

Thanks
[Magisk] pndwal:
I'd read thru that thread... users reported last builds working ok were Magisk 21.4 + Magisk Manager 8.0.7...

I notice Canyie supplied last test app 19 day's ago, and no-one has reported testing. ☹️

He needs testers with old devices!

Why don't you test app (last post, https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-985646477 ) and supply requested logs?... Could be fixed already for all we know!... 😜 PW
[Magisk] dcarvil:
My S5 G900T works fine with LineageOS 18.1 and Magisk 23.0. I rooted by flashing the Magisk zip with TWRP 3.5.2_9-0.
[Magisk] Renate:
Ok, let me state my case more succinctly:

It's impossible to replace/nullify various *.rc files in root by using replacement/empty files in /overlay.d in the ramdisk.

Any *.rc file in /overlay.d in the ramdisk will be ingested (rc_list.push_back) and deleted in load_overlay_rc() in native/jni/init/rootdir.cpp

I propose that the logic be altered:

for(files in /overlay.d)
{
if (file is "init.rc") delete /overlay.d/init.rc;
else if (file in root exists) replace file;
else if (file is an rc) {rc_list.push_back; delete file;}
else; // nothing
}
[Magisk] zgfg:
You should go to Github (link from the Magisk app) and open the issue as suggested improvement
[Magisk] pndwal:
& @MartK87

Yup, good point! 👍

Issue indicates problem is likely a sepolicy issue on armeabi-v7a devices and "sepolicy live patching will crash Samsung kernel (heard from topjohnwu)". Custom kernels will probably fix this.

https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-964156713

Here is Los 18.1 for Galaxy S5 klte and other variants:

https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-84902713

Why settle for a Marshmallow when you can have Red Velvet Cake???

Confirmed Magisk root working w/ LOS:

https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-933860365

and

https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-86126223

... Anyone for Tiramisu?

https://www.xda-developers.com/google-android-13-t-tiramisu-dessert-name/

😀 PW
[Magisk] zjbbhsso:
HTC 10, stock rom, locked bootloader and s-off can pass SafetyNet with SuperSu and Xposed installed

pass time: 00:33 UTC+8, Sunday, 23 October 2016

Root Switch Patch (follow README.txt except sideload SuperSU.zip)

Flash stock boot.img (make sure it's cleaned)

Flash SuperSU 2.78 SR1

Reboot

Flash Magisk v8 (it autogenerated custom_ramdisk_patch.sh, so it's overwrite the one in Root Switch Patch)

Flash xSetProp 0.2 (if bootloader is unlocked)

Reboot

Enable Magisk Hide in Magisk Manager 2.1 (it must have root access, u can check if it's really hidden in log)

Reboot

Flash Xposed 86.2

Reboot

Flash suhide 0.55

Disable root in Root Switch 1.3.1.2

Check status in SafetyNet Playground

I still can take OTA because these are all systemless, and I didn't mount /system read-write
[Magisk] jcrompton:
Do you have the "fix" posted somewhere? I'm definitely rushing but I had just sat down to mess with this stuff and didn't want to be chasing my tail
[Magisk] nkk71:
Not yet, should be up shortly, fixed pre N problem.

just wanna check a few things before uploading
[Magisk] edyny1:
Ok I'm passing SafetyNet and PoGo is running.

What i did:

Unroot thru SU apk (had v2.78 installed)

In recovery:

Flashed Magisk V8

Then Phhs superuser r259

Rebooted

Installed Phhs Superuser from playstore

Installed MagiskManager V2.1 apk

In magiskmanager settings put a check mark to hide root, Rebooted and boom Passing SafetyNet and PoGo working...but i had to disabled xposed framework cause not working for me while active. AND can't install suhide RC1 SuperSu 2.78 is not installed.

Is there any work around to that??

See Screenshots