Magisk General Support / Discussion

[paper88]

Hello together
If I tick some apps in the denylist and leave magisk app, some apps untick it themself: Android Auto, Cell Broadcast Service, Google Services Framework, Networkmanager and Tethering. If you wondering why I hide this apps, I just hide all Apps from google. Are there any limitation of hide apps in the list?

 

[J.Michael]

Hello together
If I tick some apps in the denylist and leave magisk app, some apps untick it themself: Android Auto, Cell Broadcast Service, Google Services Framework, Networkmanager and Tethering. If you wondering why I hide this apps, I just hide all Apps from google. Are there any limitation of hide apps in the list?

You are not supposed to "hide all apps", you are generally advised to hide as few apps as possible; hide an app only when necessary.

I don't know whether "hide all apps from google" means "hide from Google all apps" or "hide any app you think was produced by Google", but both are bad ideas.

In particular, hiding some Google processes can cripple Android.

There have been posts about USNF or Shamiko (not necessarily both, I just don't remember the details) removing some Google process from the deny list because it (the module, USNF or Shamiko) handled that process specially. I do not remember reading about those other processes you say are getting unticked.

 

[paper88]

You are not supposed to "hide all apps", you are generally advised to hide as few apps as possible; hide an app only when necessary.

I don't know whether "hide all apps from google" means "hide from Google all apps" or "hide any app you think was produced by Google", but both are bad ideas.

In particular, hiding some Google processes can cripple Android.

There have been posts about USNF or Shamiko (not necessarily both, I just don't remember the details) removing some Google process from the deny list because it (the module, USNF or Shamiko) handled that process specially. I do not remember reading about those other processes you say are getting unticked.

Thanks for feedback, i just heard somewehere that google could recognise root over other google apps. I check again and will untick all unnecessary apps

 

[klodfor]

Guys, can you help me? Post #39854. Magisk 17+ not work on next device:
- ZTE Blade V9
- ZTE Blade V9 Vita
- ZTE Blade A7 Vita
- ZTE Blave V8
- ZTE Blade V8 Mini
- ZTE Blade V8c
- ZTE Blade A6
- ZTE Blade A6 (Claro)
- ZTE Blade A6 (Movistar)
- ZTE Blade A6 Lite
- ZTE Blade A0622 (voyage)
- ZTE Blade A6 MAX
- ZTE Blade A522
- ZTE Blade A520
- ZTE Smart Fresh 5

confirm not work 16.7+ above

 

[klodfor]

What's the difference between version 16.7 and version 17 that caused this problem？

same question

 

[Nergal di Cuthah]

same question

These posts are from 2020 magisk has evolved greatly since then.
Please layout your question for a modern audience. State your device, magisk version android version and issue clearly.
Thanks it'll be good to provide help to you.

Especially since the first post you quoted refers to a post that at that time hadn't been created

 

[m0han]

Shamiko v0.7.3 (174), 06/04/2023
What's new:
Requires Magisk 26000+ / KernelSU 10940+
Follow root profile on KernelSU

 

[Mowca]

After updating magisk and restarting the phone, the phone goes into bootloop. No update method works... inatall .apk, twrp, directly from the app.Does anyone have a way to update correctly?
Galaxy s10e
Lineage 18.1
Magisk 23.0

 

[alexandrew74]

Hi! I have POCO M3 Pro 5G (Camellian). The only easy way to install Magisk for me is to replace the stock boot image with Magisk's repacked one and flash it together with the new firmware through fastboot (including empty verity file, by editing flash_all_except_data_storage.bat) - tried both stock MIUI 12.5 and the last 14 (Global).
But after this Magisk is continuously asking for an "advanced installation", but the "direct install" option has no effect on the phone: Magisk asks and asks for the "advanced install" and also can never update to newer versions.
Though everything that requires root works fine yet, I'm very curious why Magisk considers it's own installation as inferior and how to overcome this issue.

 

[kullurumanoj]

Hello All, Is anyone able to use nfc feature on cred or paytm? In paytm app it says the functionality isn't available due to security reasons. I'm using hml, I'm not a developer, lsposed and xprivacylua setup. Please help me in debugging the issue

 

[zgfg]

Hello All, Is anyone able to use nfc feature on cred or paytm? In paytm app it says the functionality isn't available due to security reasons. I'm using hml, I'm not a developer, lsposed and xprivacylua setup. Please help me in debugging the issue

Please , for the beginning, find a thread about Google Pay and read about USNF module and Play Integrity attesting (OP posts)

It will not work with XLua. You must even manually remove XLua remaining folder (apps detect it)

 

[J.Michael]

After updating magisk and restarting the phone, the phone goes into bootloop. No update method works... inatall .apk, twrp, directly from the app.Does anyone have a way to update correctly?
Galaxy s10e
Lineage 18.1
Magisk 23.0

How was Magisk 23 installed? Did it come as part of Lineage 18?

If you were running with Magisk 23, and you have modules installed, it is likely they are not compatible with newer Magisk.

If you can restore your original configuration -- Lineage 18 and Magisk 23 -- I think you should stick with it.

If you are determined to update Magisk, start by uninstalling, or at least dissbling, all modules while you have a working system. Then see if updating Magisk gives you a working system. Then, very slowly, find replacements for your old modules.

 

[ipdev]

After updating magisk and restarting the phone, the phone goes into bootloop. No update method works... inatall .apk, twrp, directly from the app.Does anyone have a way to update correctly?
Galaxy s10e
Lineage 18.1
Magisk 23.0

I have run into it (every now and then) updating Magisk using a previously patch image.
- Magisk patched boot image detected

Bootloop and/or a forever (infinite) boot.​

If it is just updating Magisk, use a clean (stock) boot image.
In your case, the stock Lineage 18.1 boot image.

For me, if the update failed..
- I normally flash the stock boot image back and reboot.

Since I still have the newer Magisk app (Manager) installed.
- Push the stock boot image to the device (if it is not already there).
- Use the "Select and Patch a File" option to patch the stock boot image.

- Stock boot image detected​

- Pull the new Magisk patched boot image.
- Flash (install) the new patched boot image.

---

To complicate my reply.

Depending on the device..
I use the hardware key-combo to boot into bootloader.
- Flash the current stock boot image to the device.
- Use fastboot to 'boot' a previously patched boot image.
- Then use the "Direct Install" option to install.

- Stock boot image detected​

Hope it helps more than confuse.

Cheers.

 

[baselmagdy]

hello, magisk isn't showing me themed icons when in shortcut mode any fix?

 

[ipdev]

Hi! I have POCO M3 Pro 5G (Camellian). The only easy way to install Magisk for me is to replace the stock boot image with Magisk's repacked one and flash it together with the new firmware through fastboot (including empty verity file, by editing flash_all_except_data_storage.bat) - tried both stock MIUI 12.5 and the last 14 (Global).
But after this Magisk is continuously asking for an "advanced installation", but the "direct install" option has no effect on the phone: Magisk asks and asks for the "advanced install" and also can never update to newer versions.
Though everything that requires root works fine yet, I'm very curious why Magisk considers it's own installation as inferior and how to overcome this issue.

I have run into if once or twice.
Sorry I do not remember exactly how I fixed it.
Might have been fixed in Magisk.

The message comes when the current Magisk (demon) is out of sync with Magisk.
The last time I ran into it, I do not remember what fixed it.

Try clearing cache and data of the Magisk app.
Assuming it is the same version that is patched into your boot image.

Clear the cache and data of the Magisk app and uninstall the app.
Reboot and install the Magisk app again.

Delete /data/adb and let Magisk recreate it.
This will kill all modules and Magisk settings.

Good luck.

Cheers.

 

[m0han]

......Yup... It's a choice... Much like Google's device integrity APIs and key attestation models really.......

Key Attestation app update v1.4.1

Security vulnerability fix: https://github.com/vvb2060/KeyAttestation/commit/c3cf23694e41ab374744559839bd86ed468f952c

 

[pndwal]

Key Attestation app update v1.4.1

Security vulnerability fix: https://github.com/vvb2060/KeyAttestation/commit/c3cf23694e41ab374744559839bd86ed468f952c

Yeah, I tried that last night... Either the fix is incomplete or I'm missing something as B/L status is still bypassed using LSP TEE Hide module... PW

 

[zgfg]

Yeah, I tried that last night... Either the fix is incomplete or I'm missing something as B/L status is still bypassed using LSP TEE Hide module... PW

Null pointer exception for me with this latest v1.4.0 and v1.4.1

 

[chiteroman]

Yeah, I tried that last night... Either the fix is incomplete or I'm missing something as B/L status is still bypassed using LSP TEE Hide module... PW

The old module TEE Hide just throw an exception in getCertificateChain method, so apps can't know if bootloader is locked or not. I will try to update AttestationSpoofer to bypass (again) the locked bootloader. They are using another cert class, because it doesn't call this method like previous versions.

 

[shoey63]

Doesn't like ROG 3