yashsingh1/xdaforums huggingface dataset:
[Magisk] RonnYap:
Jus test n see bro..For me now i can use it..

I mean after complete flash untill suhide0.50 wit exposed

of cox switch root must pass when disable root n tick su daemons ..if need to root back ..must reboot pone.

Now i jus continues flash magiksv8 phhsupersu..

then i reboot..

uninstall supersu app n install phhsupersu..

Allow phhsupersu to root

reboot..

Complete

Jus use switch root

to enable n disable root..

dont 4get su daemons must alwy tick..

Jus ignore switch root appears magiks is not fully support..

[emoji12]
[Magisk] margentieri:
I'm having trouble using Magisk's built-in busybox. None of the applications I use that require busybox will work, with all of them reporting that busybox is not installed. I see that others have been experiencing the same issue. Has anyone found a way to make the magisk busybox visible to other applications?

I'm using magisk v8 with the "enable busybox" feature checked, magisk phh root r259, and in case it matters, on a Samsung Galaxy S5.

Also, I know the hidesu feature in Magisk doesn't work for all devices, but has anyone had any luck on a Samsung device? Even with xposed disabled (disabled both individually and also simultaneously in the xposed installer app and in magisk manager) and no other magisk modules installed other than phh root, I can't get my device to pass SafetyNet :/

(Btw, can anyone tell me what is meant by PATH, as in "Make Magisk's built-in BusyBox be visible in PATH"? The only path I can think of is the path to a folder/file or the graphics path class, but neither of those seem to be the case here)
[Magisk] Artim_96:
Well, have you restored the ROMs stock boot.img? And was root installed to /system? Then you need to use the unsu.zip by osmosis, it removes system supersu.

And also tried manually wipe cache and dalvik cache?
[Magisk] silvercat:
I had the same issue with SR1 but after changing to SuperSU V2.78 stable version it is fine now. Yes the flashing order is correct.
[Magisk] andrew2432:
[MENTION=2416316]margent[/MENTION]eari

S5 sprint variant. Gonna get this working this weekend I hope
[Magisk] WeirdSoup:
With v8, the apps cannot detect the busybox, and ask me to install it from play store. How can I fix it?(as you can see, I didn't touch the option.)
[Magisk] FreeTheWeb:
S7 edge sm g935f

Stock room

Magisk 8

PHH r59

Xposed 86.2 systemles

Rootswitch

And safetynet is passed :D
[Magisk] RonnYap:
My new method..

My rom cm13 note 3 hlte

Flash Magisk V8 and phh-superuser-magisk-r259.

Install Magisk Manager and disable magiks hide

Reboot

Recovery again

Terminal type

echo "SYSTEMLESS=true" > /data/.supersu

Flash SR1 Supersu V2.78

Reboot

Recovery again

Flash suhide 0.50

Reboot

Recovery again

Flash exposed systemless 86.2

reboot

install root switch..

open root switch and jus ignore yhe word magiks is not fully support..

Before disable root, all root app need to grant before disable, otherwise will get error no su.. or need to reboot pone to get back root..

Everything root r grant now u can jus disable root..( app still root, just cannot edit if still disable root)

jus tick stop all su daemons..

If need root, jus enable it ( No need reboot)

Disable root will pass ur safetynet...

Sorry my poor language n typing take a few minutes..

But worst it.. Just try.. :) :o
[Magisk] AbiDez:
Yup, I use 259.. Yes your steps right when you on stock without twrp...

For me I have custom rom and twrp installed...

I restore only stock boot.img, flash in twrp magisk v8 for patching boot.img, flash phh superuser 259.. Reboot, install magisk manager, install phh superuser app... Start superuser app for auto grant access, start magisc manager, activate Hide mode, activate phh module... Reboot... Test Safetynet and pass...

CarHDRom V.24.7 by Carotix S6e
[Magisk] mika91:
Hello guys,

Just bought a new HTC 10, and I'd like to give magisk a try, after having plaed with custom roms.

So I restored both stock sytem and boot, then flash magik and phh supesu.

after reboot, no luck I can't get the OTA!

I then tried to flash stock recovery, but it doesn't change.

I have a stock 1.80 with systemless magisk an phh, but can't get OTA.

What do I miss?

Thanks
[Magisk] Captain_Throwback:
What does Magisk have to do with taking an OTA? I think you're in the wrong place. If you're getting an error message, search your device forum for help. Your issue seems to be device-specific.
[Magisk] mika91:
I just wanted to know if installing magisk prevent to receive OTA :confused:
[Magisk] Blauhasenpopo:
Hi....have a Huawei p9 Lite with stock rom and twrp recovery....want to play Pokemon go and will use Safety Net and i want to use xposed Framework.

So i read through the last 20 Pages, but could not find a guide what i need to install(so that all of my Prog will run) and in what order i should install these Progs?

Have downloaded Magisk V8 and Phh superuser r266hidesu.zip.

Please can someone give me a guide?

Thanks
[Magisk] jcrompton:
I see you posted that your devices are running M ....

Does that mean that we (I ) may have better much running / experimenting on all this stuff with M ROMs? Are you using stock, aosp, or CM or all three?

I have some time today so I want to try this module but I'm currently on an N ROM
[Magisk] :
Magisk v8 works fine with my Galaxy S4 I9500 GearCM13:

Magisk v8

SuperSU 2.78 SR1

Systemless Xposed 86.2

Root switch

SafetyNet passed green. PoGo works.
[Magisk] nkk71:
wont currently work on N, I'm trying to fix it....
[Magisk] AbiDez:
When you rooted with SuperSu you must first remove it over SuperSu app, install Magisk to flash and patch a new boot.img... Flash phh superuser and reboot, install phh superuser from play Store. Install Magisk Manager and activate hide mode. Reboot.... I don't use xposed because some people say it is installed, Safetynet (pogo) won't pass.

CarHDRom V.24.7 by Carotix S6e
[Magisk] Captain_Throwback:
No.
[Magisk] mlcampbe:
Is Magisk needed only for supersu and xposed

Altight I have given up trying to get android pay to work on my Verizon note 4 that has been rooted. I have the PaulPizz rom with systemless xposed, and phh superuser installed but can't get past safetynet. Given this is a on/off again problem I have decided that it is not worth it to try to keep up. Therefore all I am now interested in is keeping xposed and phh superuser installed. My question then is do I need to keep Magisk and Magisk manager installed just to have xposed and phh superuser? If not what is the best way to remove these while keeping the others.
[Magisk] nkk71:
well fixed it (kind of), currently works on Android N, but it broke compatibility with pre N, so let me fix that if i can.

No point in having 2 binaries, if I can manage to put them in 1 ;)
[Magisk] VirginPC:
Hi, thank you for ur reply......

https://github.com/topjohnwu/Magisk/releases/tag/v23.0 This is the version in the 1st place........ With Magisk Hide (SAMSUNG NOTE 8)

1st Step that i remember....

Then I download this https://github.com/topjohnwu/magisk-files/tree/canary and direct install from the apk it self, never uninstall the old Magisk (With Magisk Hide). After that i open this version of Magisk and it looks the same as my 1st question attract pic..... Then when i click on the old Magisk icon v23.0, the new installed Magisk Icon gone....... Then everything back to the old Magisk.

2nd

Me uninstall the v23.0 Magisk without remove Magisk hide (not uninstall using the Magisk app, just normal uninstall from phone (never see any uninstall option on Magisk app b4), then install the version from step 1........ End result same as my 1st question attract pic.

3rd.

After that i just install between version 23.0, Canary & Alpha for many time....... Even try to install from TWRP free times (install the .apk file from TWRP), but still same as pic........

Now,

All my app with root access break, other app like bank app still detect phone as root....... cant even boot into recovery mode on LuckyPacther coz root access break.......

Hope my explain is good enough for you to understand......... Thank in advanced.......
[Magisk] F308:
My 2 cents.

Wasn't it said that if Magisk was hidden, (feature available earlier) , then new installation is confused because all of the sudden you have two Magisks on your phone?

Situation similar to two drivers in the car.

I might understand your explanations in wrong way, yes.

Happens sometimes.

If you write about module magisk_hide it is different story.

This feature may function even if Magisk itself went to hell.

There were threads about it.
[Magisk] pndwal:
It may be chaos, but...

- It's a chronological catalogue of general Magisk support and discussion notes in one place.

- It contains answers to nearly every Magisk issue.

- It can be searched by keywords and by specific members to narrow down pertinent results, especially when members recall earlier discussion.

- Contributing members can and will continue to use this thread as a database of issues / solutions and already have their own methods of keeping track or tracking down such previously proffered help.

- It has enough active contributing members happy to help others to make it an effective means of obtaining timely solutions for issues encountered by the newbie or the experienced user.

- It is one of Magisk's most valuable resources for the above and more reasons. As a couple of examples of more:

- It provides an interesting diversion simply due to opinions / conjecture / ideas / poppycock / claptrap / balderdash as well as the notable and salient comments on all things Magisk.

- It has modern moderators, modestly making minor modifications to misdirected, misconstrued or malevolent members mumblings...

Why close it? 😬 PW
[Magisk] vandyman:
Yeah, I am done with the ranting.

Post 49411 shows what I was trying to stop. The poor guy read all the different ways and now he is stuck and no one wants to help him.

My apologies sorry for the mess I have created, was trying to do the right think.
[Magisk] pndwal:
Ok; you almost certainly have "dual conflicting app syndrome afflicting more Magisk users that covid does" as mentioned.

See

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

and

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

Nb. You may find renamed Magisk App is simply 'Settings' (default) or something you chose; uninstall all of them before reinstalling or rebooting.

Nb.2. Seems you have now messed up Magisk (mask) installation itself with different installations. After fixing dual App issue you can likely simply reinstall Magisk mask, but if you have issues you may need to do complete uninstall first... It's the big red button in the middle of the Magisk App home screen. 😀 PW
[Magisk] zgfg:
Don't take me wrong but why don't you help to that poor guy🤩
[Magisk] pndwal:
Did you create a mess?... or just an interesting diversion?... Reckon you contributed a number of good points to the general Magisk discussion... No need to apologize... not to me anyway!

And you certainly didn't create the chaos! 😝 PW
[Magisk] VirginPC:
Hi, the magisk hide is a on off button in Magisk, after turn on, then we rename magisk to other.......

But now me totally loss, and dont know where to start.......after uninstall magisk from the phone setting (not inside magisk, coz i cant find any unintall button in magisk it self) I go to samsung app, uninstall magisk, and try to find any folder name with ''magisk'', but no luck(using Mixplorer)....... coz i want to delete any left over folder.......
[Magisk] pndwal:
You need to remove all Magisk apps, 'hidden' or not to resolve Magisk Installed = N/A issue before worrying about Magisk mask itself.

In device settings you need to locate app(s) / manager(s) you may have hidden. Could be named 'Settings' or other if you changed default hide name; It most likely DOESN'T include 'magisk' in the name! Tip: check ALL apps in device settings applist. Turn off View system apps.

Don't confuse 'Hide the Magisk app' / 'Restore the Magisk app' with MagiskHide toggle.

Uninstall Magisk is the big red button in the middle of Magisk App home screen, but it won't find and remove previously hidden / conflicting apps. You need to do that manually... PW
[Magisk] ipdev:
From one of your other post, you mention you are using a Realme 7 Pro.

That device should support hardware attestation so you will need the USNF module.

Since you are using a factory system (rom), USNF should be enough to pass SafetyNet.

Just to recap.

When using USNF module.

Enable Zygisk in Magisk and reboot.

Install the USNF module and reboot.

You do not add anything to the Magisk DenyList.

---

The errors you are having with the MHPC module leads me to believe your Magisk install is borked.

Yes it can seem like it working fine but, if one root related app or module is giving error. The Magisk install might be partially broken.

You can try to delete the magisk database file and reboot. (It will be recreated on boot.)

Completely uninstall Magisk, restore your stock boot image and start clean.​

As requested in the MHPC thread, give logs in the MHPC thread.

That will allow someone to figure out why MHPC is failing for you.

If you get Permission denied as root, you have bigger issues than trying to pass SafetyNet. ;)

The USNF module will reset (hide) the correct sensitive props to pass SafetyNet but, it will not reset them all.

Even running a factory (stock) system (rom), you still might need to reset (hide) other sensitive props.

You can do it manually with a boot script(s) or just use the MHPC module (once you get it running) to do it for you.

Cheers. :cowboy:
[Magisk] pndwal:
Bit further on Magisk Installed = N/A issue for @VirginPC or others.

I recently had this issue persist with no hidden app remaining.

I had downgraded an alpha build w/ Zygisk to old 23.0 (direct install w/ existing root) and worked out that mismatched /data/adb structure (likely in Magisk db?) was causing daemon not to start. (Calling CLI Magisk -c in Terminal Emulator did show 23000 version binary.) I suspect this may also occur downgrading to 23000 or 23001 from TJW builds w/ Zygisk also.

I solved it simply by fastboot flashing Alpha-patched boot image back and restoring Alpha app, and root was restored. This restored app Uninstall Magisk function for effective downgrading also...

Alternatively if root cannot be restored, deleting /data/adb/magisk.db or whole /data/adb/ directory using TWRP or other in this situation should allow Magisk to be restored / restore itself on reboot...

Hope it helps. 😛 PW
[Magisk] pndwal:
Wondered why Magisk progress seems to have stalled for some 8 days? This:

So all is not as it seems it seems... John has indirectly been laying groundwork for big Magisk App changes...

Just a little more light on the Magisk roadmap here... Thanks John! 👍 PW
[Magisk] rodken:
This should help a lot of folks who are "in the know" and those who clearly are not.
[Magisk] pndwal:
@zgfg, others, regarding:

Broken in-app Search This Thread function

Here is a great find / tip / workaround / bug-bypass:

I had noticed orange * (ie. a link) but never thought to click it!

Still, Search This Thread button itself (coding) is broken and needs to be bypassed with extra steps. Ironically it seems it was introduced to reduce steps. 🙄 ... I'd love to see it working as intended and intuitively. PW
[Magisk] zgfg:
Ok, so

How to "Search this thread" for idiots (like me)

1) Scroll to the top and chose "Search this thread"

To save your time and frustrations, DO NOT fill the Keywords box with a keyword you really want to search for - just leave empty and click to Search

XDA will return 'results' but for ✳️, LITERALLY saying:

"Search results for query: ✳️"

Since ✳️ replaces anything, it was 'found' in each and every post - hence ignore these 'results' and proceed to the step (2)

(Even if you bothered to fill the Keywords box with what you wanted to search for, XDA would ignore and would always provide results here for ✳️, i e., would always list here ALL POSTS from the thread, thus listing 40K+ posts for this Magisk thread here - no use)

2) Take a look again to the result from the step (1):

"Search results for query: ✳️"

Depending on your screen resolution and font size, asterisk ✳️ might be right or left (in the next line) - doesn't matter, now you have to CLICK to that ✳️

A new and expanded search will open, and here you finally have to fill the Keywords box with what you really want to search for

Also, adjust the criteria - IMO better select "Most recent" instead of "Relevance" or "Date" and click to Search

All kudos to @IronTechmonkey for inventing the trick

---

Btw, in step (1) you might click Advanced instead of Search

Advance search will open and you could take the tab "Search threads"

Now you are directly in the search like in (2) above, but missing here the option to search THIS specific thread - hence unfortunately you must always go through the two steps as above
[Magisk] pndwal:
Actually, I agree that this find / tip / workaround / bug-bypass is quite limited in value, and by no means fully resolves search issues.

Perhaps it's not 'great', but it does work as advertised 🤪 ; and yes, 'Restrict search to specified thread' is missing after using 'Search threads' tab at any stage, not that a means to specify or the 'specified thread' was ever shown either...

This is, however, in keeping with XDA app's frustrating / broken functionality in general, eg inability to return to a previous page, including search result list page after checking one result (forces you to re-do whole tedious search process for each time you look at a result!), due to both back arrow and back button not doing / allowing this or even working as expected, and often landing you back in the dumb 'partial thread' view...

For now, I'll continue to do most XDA posting & searching in browser. For practical purposes, XDA app sadly only has advantages for notification functions and browsing posts for me... lends itself largely to those who don't bother either searching or posting much... ☹️ 😜 PW
[Magisk] JacobBoi_:
Hello agin,

I'm sorry for this ammount of messages but...

What are logs?
[Magisk] J.Michael:
Look at @Didgeridoohan's extensive troubleshooting guide.
[Magisk] HippoMan:
Thank you very much for all this!

Somehow, it seems appropriate that doing searches in this thread is something of around the same level of complexity as trying to figure out how to install and use Magisk these days. :)
[Magisk] brody6104:
Hi all! I have a Eonon GA2187 android 10 headunit. (It's really Alps FF-5000 8227l Android 8.1) Its rooted with Magisk 7.1.1. I attempt to update it and get the error of unsupported magisk. Please see attached pics. Can anyone please help?
[Magisk] ipdev:
Logs (log files) is a record of what the device is actually doing.

You can look at the Magisk log in the Magisk app.

It is the third option (bug icon) on the bottom bar.

On the top of the screen you have the save (disk icon) option to save the Magisk log to a file.

You also have the delete (trash can) option to clear the current log.​

Didgeridoohan gave you a link for gathering the log files for the MHPC module.

MHPC Logs - GitHub - Link

To report an issue/bug with Magisk, you would need to follow the Magisk Installation and Troubleshooting guide

Asking for help/reporting bugs - WebSite - Link​

The logs will show if the problem is with the MHPC module, Magisk or something compleatly different.

I will continue in the MHPC thread to keep things a bit more on-topic.

Cheers :cowboy:
[Magisk] J.Michael:
Like it says, the new version of the Magisk Manager app does not support the version of Magisk you have installed.

I think the easiest option is to uninstall the new Manager app and reinstall the Manager app you were using before.

If you can't stand not having the latest version, you will need to research whether the latest version of Magisk works on your system (hardware and operating system). If it does, you will need to reinstall Magisk.

Maybe start with "Why do you want to update Magisk?"
[Magisk] pndwal:
This:

https://www.didgeridoohan.com/magisk/Magisk#hn_Unsupported_Magisk_version

More:

https://www.didgeridoohan.com/magisk/Magisk#hn_Prerooted_ROM

😀 PW
[Magisk] brody6104:
I want to update because none of the modules will install because the version is too old 😔
[Magisk] DiamondJohn:
Am I missing something, or is it simply a case of updating the magisk app? and not just Magisk as he has already done. He is running v7.1.1 of the app, with v22.1 being available.
[Magisk] zgfg:
IMO, 7.1.1 cannot be Magisk version but version of the old Magisk Manager (that is the app = UI)

I don't recall the details anymore - you have to investigate yourself the releases of Magisk Stable on Github - Magisk Manager was separated from Magisk up to the Magisk version v22.

The corresponding last version of Magisk Manager was v8.0.7 or so

Hence you should distinguish the Magisk version (probably something around v19 or v20 or so in your case from the old Magisk Manager version (didn't you say 7.1.1).

You see, totally different numbers and format.

The old Magisk Manager must also show both, its own version and Magisk version.

You can also read the Magisk version from Terminal by commands:

magisk -c

or

magisk -V

By looking to Github:

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

it seems that you can easily download Magisk back to v21.2 and the corresponding Manager back to v8.0.4

On the other side, most modules should be ok with Magisk v20.4 or higher

It means that you might try if Magisk v21.4 (corresponding Manager v8.0.4) supports your device.

If it does, it should be enough for the modules

I can't help you further - would you need to uninstall your old built-in Magisk (bad practice for ROMs) and how (would it work by taking Uninstall Magisk from the Manager or by flashing uninstall.zip), and do those Magisk version around v21.4 still support your device.

Might be that your built-in Magisk was customized by some developer to make it work on your device
[Magisk] vandyman:
^^^^ Good information, I learned something today. 👍
[Magisk] pndwal:
@brody6104

If this info hasn't helped, I recall that old Canary builds will see 22002 as latest, and after updating both App and Magisk (mask) will then show real current latest build.

I suspect Stable channel is simply allowing you to see an App build (22.1) too late to support your 20.3.

I'd manually download and try to install earlier stable App / Manager builds (as already discussed) before trying Direct Install to update Magisk mask. I suspect 22.0 may work. Go to Releases at end of Magisk GitHub home page.

Also, Im a little confused by your initial screenshots. Does the 3rd one show successful Direct Install, successful Select and Patch a File only or other? If Direct Install, did you reboot the system?

Of course you may have other issues compounding this, eg pre-rooted ROM. Please see wiki links above. PW
[Magisk] curiousrom:
Why not link to the source of that quote? ;)

https://twitter.com/i/web/status/1469266621768212487

***