yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Telegram links:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85229385 👍 PW
[Magisk] forumi0721:
Hi,

I hide a magisk but some apps found hack...

I guess that use logcat message.

So uninstall app, it works.

But after reboot. magisk auto install...

So I wonder, There's way to prevent auto install magisk after reboot?
[Magisk] chrisg4:
For Po/Go basically but i'm so sad that is not working
[Magisk] gudenau:
Seems to trip safteynet itself. That's a shame. :-/
[Magisk] rignfool:
This is not a magisk issue...

This is a you need more hacking...

You would benefit from ARISE... However it's not magisk friendly as of now
[Magisk] topjohnwu:
Magisk-v8 is live!

You should receive the update in your Magisk Manager.

This release is aimed at native Safety Net support for Magisk, release notes here

BTW, I think I'll actually use my Twitter more often now lol, if you're interested, you can follow me @topjohnwu
[Magisk] waylo:
Thank you for all your work!

I was wondering, you state that for SuperSU integration, "Magisk will create a script placed in /data/custom_ramdisk_patch.sh when SuperSU detected"

If someone has an encrypted /data partition not accessible until system boots up, would this still be possible, if flashing everything in TWRP?
[Magisk] zzzhead:
I'm having issues with new magisk v8

Using oneplus 3 resurrection remix on boeffla-kernel.

How I installed using v7

1. Flash rom

2. Flash boeffla-kernel

3. Flash systemless su

4. Flash magisk

*if I stop here, I will not have root

5. Flash systemless su

Now I have root and magisk.

With v8

1. Updated from app - reboot and lose root

2. Flash systemless su - failure when creating ramdisk backup, aborting

Somehow, even with flashing boeffla-kernel and reflash systemless su, still getting failure when creating ramdisk backup.

Also tried removing su.img, magisk.img, magisk and su folder but error still there. Had to revert nandroid to older version to get root to work
[Magisk] jumpcom:
ONEPLUS 3 FreedomOS OOS 3.5.2

With v8

Always boot to recovery , seem like boot fail
[Magisk] topjohnwu:
Do you have a recovery log?
[Magisk] zzzhead:
Pmed
[Magisk] Iceyogurt:
I think it's the Magisk hide which makes root lost after reboot.

Oneplus 3, OxygenOS 3.2.7, stock boot. SuperSU+Magisk v8+Xposed systemless. No suhide.

I lost root after reboot when Magisk hide was checked, and regained root after Magisk hide was unchecked.

Edit: sorry, I rebooted again and everything works well. Weird.
[Magisk] chudy_85:
[MENTION=4470081]topjohnwu[/MENTION] Thank's for v8 it's pass sefetynet

How I do :

Flash Magisk v8

Flash phh's v259r by topjohnwu

Reboot device

Install supersuser v2.0beta9

Open Magisk and permission root forever

Go to settings and select hide Magisk and enabled busybox

Reboot device

Check safetynet and here pass

HUAWEI MT7-L09

Edit

When I install xposed v86.6 systemless it's don't pass safetynet
[Magisk] H4X0R46:
So, I just installed Magisk v8 and phh's superuser module. It says I don't have root? Am I supposed to have root before hand?
[Magisk] soder:
OK. I will try to make this post as well written as possible. This morning I saw there was updates to both Magisk (v7=>v8) and Magisk Manager (v2.0=>2.1). It was morning, and I just updated and rebooted. After that I read that I shouldn't have done that.

Since I no longer had root (I lost that during the Magisk update) I manually flashed the boot.img from the rom.zip via fastboot and I also run a magisk uninstaller. I also reflashed my rom just in case.

I now wanted to everything correct and clean, and I want to follow this que:

1. Stock rom and boot.img

2. Flash SuperSU in systemless mode and boot.

3. Flash suhide and boot.

4. Flash Magisk and Xposed systemless

Well, right now I'm at step 3, and I wanted to see with SafetyNet before going on with Magisk. The problem is that I fail, and I wonder if there's some kind of new update to SafetyNet that fail SuperSU+suhide even without Magisk or Xposed?

EDIT: I forgot the 06suhide path. Will try that.

EDIT2: That wasn't enough.

EDIT3: How strange. Without Magisk and Xposed I didn't pass SafetyNet. With only SuperSU, suhide, 06suhide I didn't pass SafetyNet.

If someone want to try to explain for me why that happened would make me glad. =)

/Söder
[Magisk] FRooter:
To confirm, did you explicitly configure suhide, or just install it? Check output from /su/suhide/list via Terminal Emulator -- refer to the suhide thread for further detail and troubleshooting. I have a similar combination but without Xposed and without MagiskHide with SafetyNet passing. FWIW I blacklisted via both UIDs and process names.

SuperSU 2.78 SR1 installed via recovery, then boot

suhide 0.55 installed via recovery, then boot

Configure the suhide blacklist then reboot

06suhide modification, installed via Terminal Emulator

Reboot or execute /su/su.d/06suhide once via Terminal Emulator

The above passes SafetyNet at the time of posting.

I then installed Magisk 8 via recovery, booted, and observed SafteyNet checks still pass via SafetyNet Playground and SafetyNet Helper.

I don't have any additional Magisk modules installed at the moment.
[Magisk] Ninoh-FOX:
For magisk v8 work with supersu 2.78 you must mod update zip, you must inject in v8 roothelper folder from v7 and update-binary mod with code from from v7 and v8.

http://cloud.tapatalk.com/s/58075889c6047/Magisk-v8_mod.zip

V8 mod for work with chainfire supersu and suhide

Enviado desde mi E5603 mediante Tapatalk
[Magisk] rhyzan:
Heya [MENTION=4470081]topjohnwu[/MENTION]! So I have some problems in adding some processes and package names in MagiskHide. If I enter the command to view the list, this would show up in root shell

/magisk/.core/magiskhide/list[4]: cat: /.core/magiskhide/hidelist: No such file or directory

Now, if I try to add some random potato app, this would show up in root shell

1|root@klte:/ # /magisk/.core/magiskhide/add com.somefakkin.app

grep: /.core/magiskhide/hidelist: Bad file descriptor

/magisk/.core/magiskhide/add[9]: [: 0: unexpected operator/operand

Checking the file (hidelist) will only show the default entry which is SNet. Attached in this post is the logcat from Magisk Manager.

here's my setup (zips flashed [cleared out caches and /system only] in order in TWRP, booted only once after everything if flashed)

SM-G900L

CyanogenMod 13 08/20 Snapshot with Bank GApps

DivineBeats 8.0 (System)

SuperSU 2.78 SR1

SuHide 0.55

Magisk v8

Systemless Xposed 86.6

I'm actually doing it all again but I would let SuperSU boot first then flash Magisk. Is there anything that I miss? Pardon my ignorance if I did :)
[Magisk] higedamc:
Hi, thnx for uploading this zip but how can I use this? v7 → flash this zip → flash v8?
[Magisk] soder:
You might have to tell that it may need this mod if just upgrading from Magisk v7. If restoring boot.img and root again and installing Magisk v8 again it wasn't needed for me?

/Söder
[Magisk] steveo17:
V8 would not boot for me.

I flashed it over v7.

Nexus 6P

Unlocked

Supersu 2.78

Magisk V7

SuperSU Hide .55
[Magisk] Ninoh-FOX:
For mod (oficial not work to me) only install in twrp recovery over magisk v7.

Enviado desde mi E5603 mediante Tapatalk
[Magisk] jaccydan:
https://xdaforums.com/t/module-magi...p-edits-and-more-v6-0-1.3789228/post-85585341

Just a note to say that my Magisk SafetyNet and hence Google Pay was failing. Followed the youtube video above and it's now working again. However I'm not having Google Play Certification showing.

If anyone knows how I can get that setting back it would be much appreciated.

*(Don't say I've posted to the wrong thread again!) :rolleyes:
[Magisk] Didgeridoohan:
If Google Play Store certification isn't showing, it's usually just a matter of time before it shows up. Wait and it should show up there eventually, and as long as you pass CTS it'll be certified as well.
[Magisk] 73sydney:
Prolly still more suited to the Google Pay threads

But from my own module notes about Google Play Certification, as part of Google Pay troubleshooting:

Clear Play Store & Play Store Services Data & Check Play Store Certification

Toggle Airplane Mode on

Clear data and cache of:

Google Play

Google Play Services

Usually this will be achieved by (exact steps and terminology may change per device or ROM):

Opening Settings

Going to Apps, choosing Show All Apps

Enabling Show System Apps via a menu option

Locating the app, tapping it and then finding Storage/Cache

Tapping Clear Data

Reboot (Best) and/or Toggle Airplane Mode off

Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom
[Magisk] jaccydan:
Thanks @73sydney that method worked for me, it now shows Certified in Google Play.

Everything is back to normal - SafetyNet passes in Magisk and SafetyNet Test apps. I have just used Google Pay successfully online.

Apologies again with my thread posting, I have trouble at times finding the exact suitable threads for my queries.

Anyway, you guys are great on here! You've solved this issue. Can't thank you all enough! :D 🙏

'Til the next time..
[Magisk] Daddi8989:
Have you tried to rename magisk from settings?

This helped me out with some apps ;)
[Magisk] jm_sanders:
hello ,

my phone is a MI 9T model M1903F10A, so it is a chinese K20 flashed with a global ROM.

One Year ago I faced problems installing magisk following the advice here https://github.com/topjohnwu/Magisk/issues/2492.

A couple of days ago I updated to MIUI 12.1.4.0 RFJMIXM (STABLE) Android version 11 RKQ1.200826.02.

Installed Magisk 23 by patching the boot.img and then flashed it using fastboot, the usual way.

Now I have got the following problem, it takes a pretty long time to boot and when finally everything seems ok, I notice that I can use the SIM cards only for phone calls but the mobile network doesn't work.

Disinstalled magisk and everything turned out normal.

Hope there will be a solution.

Regards
[Magisk] Didgeridoohan:
Are you sure it isn't one of you're modules that might be causing issues with the new OS release?
[Magisk] pndwal:
I don't think you can prevent this without uninstalling Magisk. daemon checks / reinstalls if missing intentionally.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85390173 PW
[Magisk] zgrzytus:
Poco X3 NFC works fine about a year, untill yesterday CTS profile failed, that worked for me:

Question - i've renamed Magisk (21.4) and after i try to run it popup "install full version of magisk manager" or sth like this but hitting ok not works... manualy install manager 7.4.5 also seems to not works, or i do sth wrong... :) (xiaomi.eu 12.0.7)
[Magisk] jm_sanders:
Thanks for the hint, yes there was an old MagiskHide module present.

Removed it, uninstalled magisk and reinstalled magisk and eveything turned out fine.

Thanks a lot

Regards

ps.:

Installed the last MagiskHide module and after reboot faced the same problems.
[Magisk] pndwal:
Also, how did you update? These issues with Sim, wifi etc are most often caused by using mismatched boot image.

As you've patched image manually and evedently re-flashed stock image manually, check you actually patched image extracted from current ROM! It's very easy to muddle the images in ADB directory on PC etc...

If you took OTA (incremental from OEM), you need to download the current ROM complete to extract boot.img (best practice) or use TWRP to take backup incl. boot partition (unrooted), locate the boot image .win file, then patch and flash that. (Should work renamed to .img or as .win.) PW
[Magisk] pndwal:
Do you mean MagiskHide Props Config module? If so, how did you uninstall it? ...

If not uninstalled properly I'm guessing Config data is still present and your prop changes return when reinstalled. - Use a Terminal Emulator, run 'props', use reset option to remove all your original prop changes... or uninstall from modules menu. 😜 PW
[Magisk] jm_sanders:
Uninstalled from modules menu in magisk app.

then

Activated again MagiskHide Props Config module, did in terminal as superuser props with option r , problem persist.
[Magisk] pndwal:
Old pre 22.0 version of Magisk and manager use obsolete hiding method, but should call appropriate stub unless you have internet/ network / firewall /adblocker etc issues...

But why such an old version? Why not update to 23.0? Should be able to use direct install ... Be sure to Unhide Manager in settings to avoid issues. I'd also suggest disabling all modules first and reinstall later. PW
[Magisk] Foxwile:
is there any way to fix safetynet pass? I've tried lsposed method, universal safetynet fix method, model_mod, latest magiskhide props and still nothing, i've cleared data from google play and play services, rebooted and still nothing... Mi 9T Pro EvolutionX Android 11.
[Magisk] pndwal:
I mean what is "MagiskHide" module you uninstalled / reinstalled? ...

If you did mean MHPC module and it's installed again, Terminal Emulator (not sure about Termux) should recognise 'props' to run configuration interface... Unless Installation is corrupt... PW
[Magisk] pndwal:
Seems old model prop change method is not working w/ such custom ROMs when the devs have already manipulated props in pre-built utils

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85580011

You could persist with XPrivacyLua method, try alternative methods

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85582201

use different Custom ROM, return to Stock ROM or wait for a solution for ROMs that manipulate props. 😀 PW
[Magisk] jm_sanders:
Uninstalled from modules menu in magisk app.

then

Activated again MagiskHide Props Config module, did in terminal as superuser props with option r , problem persist.

--In Termux need to use 'su' and a popup will appear to give root permission--
[Magisk] Didgeridoohan:
I don't see any logs posted anywhere... There's an option in MagiskHide Props Config to collect logs, and those will include a Magisk log and a boot logcat, so they're pretty comprehensive. If you're lucky there'll be something in there that hints at what's going on.
[Magisk] pndwal:
Is this the same using standard Terminal Emulator (w/ no su command)? PW
[Magisk] forumi0721:
Of course...

And I build source another name, I found..

Someone says It use logcat log parsing method.

Everything ok, when uninstall manger.

So, I want to use magisk without manager, and when I need to change setting or update/install modules. I want to intsall...
[Magisk] zozo932:
hello

I can normally flash TWRP with the latest version of OOS 11.0.3.1 for oneplus 7 but when I install magisk 23 in twrp I have an error message at the end "magisk failed to mount / system_root busy" and the phone reboots and hangs on the oneplus bootloop (the logo) I have to reboot on the TWRP and reinstall the oos 11.0.3.1 directly via the zip file and everything goes back to normal. But I can't root the phone. can someone help me or try? thank you !!!
[Magisk] Didgeridoohan:
Could be an incompatibility with TWRP. Installing through recovery isn't officially supported, even though it's often possible. Try patching the boot image in the Magisk app instead. You can then install that from TWRP and hopefully things should work after that.
[Magisk] zozo932:
Thank you so much for you reply you can give me a tutorial on how to fix the boot image in the Magisk application ! how i can found the boot.img of the latest oos ? thank
[Magisk] pndwal:
Latest @vvb2060 Alpha Magisk

Will add notes later

alpha update log​

Magic (f8f8c28f-alpha)​

Based on f8f8c28f, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Fix the default shell path of busybox

Extended update to MagiskHide

Remove hard-coded gms version number

https://github.com/vvb2060/Magisk/b...7875d415587/app/src/main/res/raw/changelog.md

I can't yet find build files hosted on GitHub or Telegram...

👍 PW
[Magisk] Didgeridoohan:
Since you have TWRP you could just make a backup of the boot partition, rename it to boot.img and then use that. Otherwise you need to find the firmware file that corresponds to your current setup and extract the boot image from there. Can't remember if the OP7 users payload.bin, but if it does it's definitely easier to do a backup in TWRP...
[Magisk] pndwal:
Installation Instruction linked from main Magisk page on GitHub is tutorial! 😀

Click Octocat icon

on Magisk App home page.

... And don't forget to thank the tutor!

😜 PW
[Magisk] Ryano89:
Your module did not work for me on my 8t with custom ROM unfortunately
[Magisk] zozo932:
Install the drivers from the mounted drive you should get when connecting the phone to your computer

On Windows you should then have a folder in C:\Program Files (x86)\OnePlus USB Drivers\Android with the platform tools (ADB.exe and Fastboot.exe) you will need, you can obviously copy the content from that folder somewhere else if you wish.

Connect your phone to your computer

Copy your rooted boot image to the folder that has adb.exe and fastboot.exe

Open a command window on your computer by right clicking in that folder and choosing Open command window here

In the command window, Type or copy/paste the command ADB devices and press enter

If you see a prompt on your phone to allow the computer connection then accept it, better still, tell it to allow from now on also.

You should see a string of characters shown in the command window, if you don't see that, then try another cable or re-install your drivers and reboot the computer.

Reboot your phone into Fastboot either by using ADB on your computer ( ADB Reboot Fastboot ) or by enabling Advanced reboot in your developer options in settings and then hold down the power button and use the 3 dot menu on the top right and choosing "Bootloader"

In the command window type Fastboot Boot <filename.img> i.e. Fastboot Boot rooted_boot.img and press enter

You should see a couple of lines in the command window telling you it's copying over to the phone, don't worry it's not being flashed or replacing your existing installed boot image

The phone should then restart and boot using the image from your computer, it will be a slightly slower boot than usual, your existing unlock method should still work

Launch the Magisk app, it should already have root access because the boot image you've used is already rooted

Go to Install under the top Magisk section

Choose Direct Install (Recommended)

Magisk will then apply root access to the boot image on the actual phone

You will be prompted to reboot the phone on the bottom right, do this to complete the process

You don't need the phone connected to your computer anymore as the installed boot image on the phone should now have root access

You can check for root either using any app which requires root or by using an app like Root Checker

this is please confirme me ! i hope i dont lose my data, image, video... ?!
[Magisk] Mowca:
installing safetynet-fix-v1.2.0-MOD helped. I'm using lineageos 18.1 for s10e.
[Magisk] Didgeridoohan:
@zozo932 That doesn't look like John's instructions from GitHub...

You don't have to make it difficult. Make a backup of the boot partition in TWRP, rename it to boot.img. Then install and open the Magisk app, choose install and "Select and patch file" and pick the boot image file when prompted. Once that's done you take the patched boot image and install it to the boot partition using TWRP.

In theory that should work fine (I've done it before), but there's always a chance of something going wrong. Restoring the unpatched boot image (unrooting) should get you out of most issues though. If there are device specific things that needs to be done you can find help with that in your device's forum.
[Magisk] zozo932:
Thank you !

i follow this tutorial : https://www.droidwin.com/patch-stoc..._the_Stock_Boot_Image_File_using_Older_Magisk

in first the phone the phone has to restart normally but in magisk I was still not root I think maybe I put on the wrong partition A. I followed your tutorial to do it via twrp, I put install image , I selected the patched magisk then category boot and from the phone bootloop on the oneplus logo ...

sorry im newbie
[Magisk] Didgeridoohan:
Restore the unpatched boot image and then check your device's forum for help...
[Magisk] MoL_82:
Thank you. The MOD worked on my S9. The Shim did not. I also tried the LSPosed/XPrivacyLua-solution, but that messed with my location.

EDIT: The MOD makes my S9 think it's a Pixel. For now that is only an issue if you want to screen security+blue button backup workaround. When I apply that, I get random reboots and it is not working.

Seems no issue when you use another backup-app or no screen security.
[Magisk] zozo932:
Its okay I reflash the original boot I have access to the phone normally but I am still not root
[Magisk] Cypherous2:
So sadly, despite me passing safetynet checks and me being able to re-add my card as a contactless payment method i can't actually make payments so sadly there would appear to be something else in play with the Xperia 1 III :(
[Magisk] ipdev:
Removing com.google.android.gms does not fail CTS right away, eventually it does.

Without com.google.android.gms hidden it will fail CTS upon boot.

The only way to keep SafetyNet passing..

(Poco F2 Pro, stock MIUI 12.5.2)

Enable MagiskHide.

Hide com.google.android.gms

Hide com.google.android.gms.unstable

Install the USNF module.

Change the ro.product.model

Note:

The bootloader and boot status is still adjusted by vvb2060's alpha f98c68a2 build.

This was removed by John in the official Magisk repo.

All builds from John going forward, you will need some way to adjust the bootloader and boot stage.​

Cheers. :cowboy:
[Magisk] Didgeridoohan:
You mean the different props that MagiskHide sets currently (but not going forward)? That's what MagiskHide Props Config v6+ is all about and pretty much the sole reason for that update to the module...
[Magisk] Didgeridoohan:
Might need this:

https://github.com/stylemessiah/GPay-SQLite-Fix
[Magisk] Cypherous2:
Already used it, google pay lets me add a card but payments fail, my banking app despite being behind magiskhide still clearly sees my phone is jailbroken, if i had to guess its just failing because its not getting a hardware attestation back on a device it knows supports it
[Magisk] Didgeridoohan:
It doesn't, that's probably just a UI bug (there's gonna be tons of these little things, and probably a few big ones as well, before I get everything together). Looking forward to your report in the module thread.

Edit: Yup... Not checking the variables properly. Simple fix, will wait for anything major to fix before creating a new release.
[Magisk] Shxckz:
where can i find a apk for this version ?
[Magisk] sergej_7:
how to Pass cts on Android 12?
[Magisk] AJHutchinson:
topjohnnwu has been hired by Google and no longer supports hiding root buddy so unless someone else starts picking it up its not going to happen 😅😥😭
[Magisk] TheKerevas:
Hi I also have an F2 Pro but I'm on the latest version of OneOS. I did not understand some things, which version of Magisk should I use? USNF module which version do you need? I have Magisk v23, if I have to install the alpha version of vvb2060 do I have to do something special or just flash from the recovery? And if I need it, can you send me the link to download it? I can not find it

EDIT: I succeeded but I don't understand how to change "ro.product.model"