yashsingh1/xdaforums huggingface dataset:
[Magisk] monicaONxda:
i've rooted it (note 10+) with the official magisk guide for "system-as-root" partitions and then encrypted it, so i have a rooted stockrom, no custom rom - thats why i debloated it and uninstalled lots of bloatware. there is no need to uninstall (via adb) or disable (via system/apps) any packages such as playstore. i just mentioned it, because i have uninstalled it before (don't need it). to check the certification you obviously need it... hope that helps...
[Magisk] HippoMan:
Got it. Thank you very much. That indeed helps!

When I have a window of time where I don't need my device to be up constantly, I will try this myself and report back. Probably it will be no later than the first week in September.

I'm hoping I can be totally (or at least mostly) de-Googled!

.​
[Magisk] monicaONxda:
Android 10 Encryption / Security Issue - ADB Encryption Bypass?

On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!

This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!

Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?

Is this issue related to Magisk? And can it be fixed?
[Magisk] andrea0807:
But when does magisk support arrive for the eu weekly Android 11 ROM?

I can't upgrade my poco F2 Pro

Inviato dal mio POCO F2 Pro utilizzando Tapatalk
[Magisk] JudgeDread11:
It comes when it's ready. No sooner and no later.

Please don't ask for ETA's it's considered impolite towards the developer.
[Magisk] palmbeach05:
What's funny is you want support for something (android 11) that is still in beta. He (topjohnwu) is pre-emptively making the changes for it, and some of that can be seen in the canary branch. But no, we must bow down to the almighty poco f2 like its a life or death situation.

Park your butt on android 10 and take a chill pill. And take the very helpful advice of checking out the canary branch release, as it does provide android 11 support.

If users don't want to use the canary branch, and they have android 11, that's on them. But the problem is that, per the first post in this thread, this thread is for stable and beta releases, and not canary. Off hand, I'm not sure if canary was added to what can be discussed or not.

Either way, the point is [MENTION=5960793]andrea0807[/MENTION] claims they cannot update his device due to lack of magisk support. Fact check, https://github.com/topjohnwu/magisk_files/blob/canary/notes.md shows that support is there. In fact, since April, support has been there https://github.com/topjohnwu/magisk_files/blob/321bcbec230211d04ce6c4c37d609ed6b4036b34/notes.md

7 individuals so far support the lack of fact checking. Keep it up!
[Magisk] FailSafeNow:
I did a clean install of my OS. Now most of my mods are working. But not the audio mods. I have James DSP and Viper installed, and they're not working at all. I have the Audio Modification Library also installed, and have tried the Audio Compatibility mod. Things just aren't working. Can anyone help?

Galaxy Tab 4, milletwifi, running Android Pie, LineageOS 16, matteo build.
[Magisk] palmbeach05:
Yawns at the boring response which missed the hepful advice given to [MENTION=5960793]andrea0807[/MENTION] regarding the canary branch (see revision on the post you attempted to use the tactics of cancel culture and public shaming on me) and moves on with life.

If users don't want to use the canary branch, and they have android 11, that's on them. But the problem is that, per the first post in this thread, this thread is for stable and beta releases, and not canary. Off hand, I'm not sure if canary was added to what can be discussed or not.

Either way, the point is [MENTION=5960793]andrea0807[/MENTION] claims they cannot update his device due to lack of magisk support. Fact check, https://github.com/topjohnwu/magisk_files/blob/canary/notes.md shows that support is there. In fact, since April, support has been there https://github.com/topjohnwu/magisk_files/blob/321bcbec230211d04ce6c4c37d609ed6b4036b34/notes.md

And the so far 7 individuals support the lack of fact checking and the attempted attack on me.
[Magisk] Spaceminer:
Uninstall all of them. Then try both viper and James DSP separately and see if they work alone.
[Magisk] palmbeach05:
To add to this, and as a question for clarification, [MENTION=10677755]FailSafeNow[/MENTION] are we talking regular viper or legacy viper?
[Magisk] Spaceminer:
I'd try both personally, but I'd try using legacy first, just because the Note 4 is an older device.
[Magisk] Z-Blade:
I am the latest canary and some of the magisk modules I can't manually install because they are grayed out and not be selected while some others are fine. Is there something I need to do or check with the modules?
[Magisk] Didgeridoohan:
What do you mean? Greyed out where?
[Magisk] zgfg:
You mean installed but disabled in MM?

I had some (previously installed, later disabled) and I just reinstalled manually From storage (also using latest Canary) - then you can re-enable if you wish (all through Magisk Manager)
[Magisk] Z-Blade:
Look at the attached screenshot. See how I can select CloudFlare and the Aux module but the Valken and OpenGL Lite module is a much darker colour? I can't select those 2 as well as the Adreno Thermal module. I am trying to manually install them from the Download folder.

Edit: I just realised they are flagged as files and not zip files. While the CloudFlare and Aux modules are flagged as Zip. Not sure how to change that. Looking at the full name, they are clearly zip files.
[Magisk] palmbeach05:
The greyed out ones are not files that magisk is able to flash, therefore it flags it, by way of greying it out, as incompatible
[Magisk] Z-Blade:
I was able to get it working. Was weird but all I did was move those files into the main sdcard directory and then move it back into the Download folder and then Magisk registered them as zip files and then I can flash them.
[Magisk] palmbeach05:
I was actually thinking do that or just move them to external and flash from there in order to fix that
[Magisk] edimonoarfa:
Where can I get this version?
[Magisk] zgfg:
tar.gz and apk files are not zips - so grayed out

But he has also some zip files (by extension) that look like (by name) as valid modules

AFAIK, MM only asks File Manager to filter for zip files (therefore not-zip files are grayed out)

Look to my screenshot: Empty.zip (0 B) is definitely not a valid module but it's not grayed out for me (I'm also on Canary)

[MENTION=4465983]Z-Blade[/MENTION]

Looks like an issue with your file explorer. Look at the icons left to those grayed out zip files - icons are different than for the not grayed out zip files.

For some reason those grayed out zip files are not recognized as zips.

Try to open them - maybe they are corrupted

Or install a third party File Explorer and Select it for navigating to modules (except now for this test I never use built-in File explorer but only MiXPlorer and never have problems)

Edit: Seeing now, as expected that it was a really your file explorer issue (not recognizing them as zip files) and you that you have resolved
[Magisk] zgfg:
You can find on GitHub, there is also another Magisk announcement thread where you can find a valid Canary download link in its OP post #1

Anyway, change the Update channel in MM Settings to Custom and put the URL:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json

Back on the main window it will offer you to update (later better revert Update channel to Stable or Canary)
[Magisk] ii9:
Hi. I have some issue to install the newest manager. The recent still works fine, so it's not a big deal, just wanted to know what is going on, if you guys know. I'm on android 10, custom rom. Since long time I haven't had any issues with canary.
[Magisk] pkgnex:
I am getting this same error. When trying to update Manager from 295 to 296, it says "There was a problem parsing the package".
[Magisk] zgfg:
All permissions (File storage) given?

Maybe Manager hidden/repacked, try to restore

Btw, latest Canary is b296.

Download the apk manually and install
[Magisk] ii9:
Well, as you said, I had a look now, and the permission section in app info is inactive, with no requested permissions written. I never had a look before, but was always fine. So not sure about that.

As well as I'm not sure what restore you mean. But I did clear the cache in the settings/apps, so I don't know if this is what you meant, but it worked. :svetius:

Also, I seem to have issues to find the canary zip/apk, since the canary thread on xda has closed. Therefore I just keep updating when it gives the notification, plus do a download zip only. Only on this way I can always have the latest zip.

Thank you for help.
[Magisk] zgfg:
Couple of posts above was (custom channel) link to always the latest Canary installation:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json

Open in browser, you will see links inside to app-debug.apk and magisk-debug.zip:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/magisk-debug.zip

Click and download them when needed
[Magisk] Alxoom33:
Same. Taimen on 11 beta 2. Looks like there's an issue with this build's Magisk Manager's installer. Probably the next MM update will fix the problem.
[Magisk] pkgnex:
I was able to get it to work by clearing the Magisk Manager app cache and re-trying the install, just as [MENTION=9458514]ii9[/MENTION] did.
[Magisk] ii9:
Aaaah okay, good to have it, saved, thanks
[Magisk] JudgeDread11:
I also had the parsing error on OnePlus 7. Didn't report since I assumed it was something with my device.

Downloading the app from GitHub and install it manually worked.
[Magisk] Alxoom33:
Yes, that worked! Thanks and thanks [MENTION=9458514]ii9[/MENTION].
[Magisk] ii9:
Thanks to zgfg :)
[Magisk] pndwal:
[MENTION=2032614]edimonoarfa[/MENTION], [MENTION=6892913]darrendude1[/MENTION], [MENTION=4793042]pkgnex[/MENTION], [MENTION=9458514]ii9[/MENTION], [MENTION=4100646]Alxoom33[/MENTION]

All Canary releases here (For manual download):

https://github.com/topjohnwu/magisk_files/commits/canary

Other files / how too navigate:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82863085 :good: PW
[Magisk] Mouchoir:
Managed to pass the ctsProfile validation thanks to this !

Amazing, good job
[Magisk] FailSafeNow:
Ok, another fresh OS install, then immediately installing Audio Mod Library, James, and Viper (Legacy: New, Material, User App, Kill All). Let's see where we are. NOT WORKING.

Let's try the Compatibility Patch. First try: skip, skip, skip, no. Result: STILL NOT WORKING. Wait. System sound effects seem to be working. Except the channels are switched for some reason. Hell if I know. Is it the headphones? No, they work right on other devices.

Second try: Patch New Logic, Remove notification_helper, don't skip, Use Lib Workaround. Same results as before. And left and right channels are still reversed. Ok, I'm open to all suggestions.

(Just for fun, or tedium, let's reboot with all modules disabled and see if left and right are still switched. Yup. Maybe my device was defective.)

EDIT!!!!!!!!!!!

OK OK OK. I disabled the stock AudioFX thing that came with the system. NOW we're in business.

Audio channels are... still reversed. Anyone got a mod that can swap left and right?
[Magisk] GuyInDogSuit:
Can't install the latest manager update. Keeps telling me, "there was a problem parsing the package." Where is the file so I can delete it and restart the download?
[Magisk] pndwal:
Try this: see my post above for manager apk files (Canary, or see linked post for stable), download your choice, simply run the apk, or uninstall your manager first if still have problems. PW
[Magisk] Slim2none4u:
Had the same issue. Went to GitHub and downloaded it manually from there and it installed fine.
[Magisk] zgfg:
This is unbelievable. Five people report the problem and all confirm how they resolved, then the sixth comes and asks for the same (parsing error on MM update) and expects that other users woulld waste their time writing him to help, while he himself didn't bother to take a look what others were just discussing preciously
[Magisk] pndwal:
Yes, and a newer solution (based on [MENTION=6345368]Displax[/MENTION]'s solution) is now integrated into MagiskHide Props Config module.

This solution will more likely keep device specific features (Galaxy Store, etc) working.

It uses a real prop value selected automatically usually from older devices from same OEM (from the extensive included list of fingerprints), and also offers ability to pick a value manually or even use a custom value, thereby providing for dead easy setting / trialing alternative prop values (eg from the included list of fingerprints) where such features are not working as expected.

See here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83148385 PW
[Magisk] exocetdj:
has anyone been able to mirror or mount optics and prism on new samsung devices?
[Magisk] GuyInDogSuit:
And you expect said person to read the previous five pages to find the solution? Unbelievable.
[Magisk] zgfg:
It was right in the posts above his question

Maybe a new type of hardware Magisk modules ?
[Magisk] Alxoom33:
We expect that you try to read! Also, understand. I read but didn't understand the solution initially. But at least try!
[Magisk] xunholyx:
An easier fix is to clear the cache

---------- Post added at 10:24 AM ---------- Previous post was at 10:23 AM ----------

See my answer above

EDIT: [MENTION=4470081]topjohnwu[/MENTION] knew of the problem and released a fixed version. Clearing the cache for MM after trying to download/install the earlier version will then direct you to the new version that doesn't have the error. I should have been more clear in my original posts
[Magisk] RebelLion_:
I am attempting to create a Magisk module to find and patch an rc file but idk if I am editing the correct file for Magisk to overlay. I got it to flash and run the script succesfully but it doesnt seem to have an effect on the actual file. The whole overlay and mount structure is a bit confusing tbh. Am i supposed to be targeting the Magisk mounted rootdir instead? For example '/sbin/.magisk/rootdir/init.qcom.rc' instead of '/init.qcom.rc'?

Heres the updated script: https://del.dog/ywicawywic.sh
[Magisk] vandyman:
That is why this thread is not supported anymore. At least part of the problem. [emoji6]
[Magisk] RebelLion_:
There is a search field for almost every website you can visit. Might help if you got to know how it works.
[Magisk] RebelLion_:
Update on this, i edited the RCFILE paths to point to the "$MAGISKTMP/rootdir/init.qcom.rc" instead and still nothing. I saw something in Magisk's Dev Guides that the Root "/" filesystem is manipulated through an overlay.d directory. Is that a directory i would make in my module folder? And then i could copy that file to the overlay.d directory, edit it and have it "overlay" the original on boot? I might try it anyways until i get an answer
[Magisk] GuyInDogSuit:
Thanks, Captain Obvious!
[Magisk] vMAC:
Anyone know what might be going on? Had the same issue as everyone else with the parse error. Uninstaller and then re-installed. Now when I go to Magiskmanager and Magiskhide nothing is there, it is blank. Went back to earlier version of ManagiskManager still same thing. Back on 296 still no joy after multiple reboots, etc. On Pixel 4XL, anyone know what is wrong?
[Magisk] GuyInDogSuit:
Try this: Go into the system settings and clear the manager's app data. When you open it again, you should be able to download a fresh copy of the apk and install it now. Had to figure that out on my own.
[Magisk] PoochyX:
Alot of things in the android world we have to find out individually cause we all do different things to our phones cuss well if we didn't want to do nothing we would of stayed on stock with no magisk

([emoji88]Chaos GSI[emoji88])
[Magisk] xunholyx:
You don't need to clear data. Clearing cache is all you need to do. If you clear data you'll need to set everything up again.
[Magisk] vMAC:
Clearing cache nor clearing data fixed the issue. Magiskhide is still empty.
[Magisk] JudgeDread11:
Maybe a silly question, but is Magisk hide turned on in settings?

If you cleared data it reverted to default settings and Magisk hide isn't enabled by default anymore.
[Magisk] Didgeridoohan:
That is a completely separate issue from the parsing problem. You've got some other problem you need to figure out.
[Magisk] Didgeridoohan:
That log shows what is happening in the background with Magisk and MagiskHide (and MagiskHide seems to be working just fine). To me it sounds like you are having issues with the Magisk Manager and that would not show in the Magisk log. I can't quite remember now if any similar reports have been made and if so what solutions there were... Some kind of permission or messed up database, maybe? Uninstall and reinstall is the classic solution. Have you done that after the issue started?
[Magisk] vMAC:
Yes I have done it about five times. Even tried earlier versions of magiskmanager same issue persists.
[Magisk] BeeJ1109:
Hi try to flash stock boot.img. then bootup in TWRP recovery again and reinstall magisk 20.4.zip .

Patches the Stock boot.img. Using Magisk Manager 7.5.1 To achieve Root again.

Sure Magisk is now reinstalled. Then enable Magiskhide in settings.

Should now work correctly again. Hide apps, add modules you require.

Cheers
[Magisk] GuyInDogSuit:
Didn't reset my settings.
[Magisk] Didgeridoohan:
Just for clarification:

That depends on what settings you're talking about. Things like which apps have been granted or denied superuser access, apps on the hide list and modules won't be reset by clearing data for the Manager. That's all kept in a separate database. But, things like app theme, download location, superuser request timeout, etc will be reset.
[Magisk] Devilix:
In the official OP thread there is write:

Ok, no probs... so:

- i have flashed SuperSU 2.78 SR1 (systemless mode)

- i have flashed magisk 7

- reboot

And now??? I have SuperSU installed that tell me "there isn't any SU binary"??? WTF?

What other things i have to flash to get a working systemless root??? Damn...
[Magisk] Captain_Throwback:
Restore your stock boot.img, delete /data/magisk.img and /data/su.img, and start over.

This time, flash the SuperSU zip. Then boot to system. Once you confirm root is working, install Magisk Manager, and let it install Magisk for you. Reboot when prompted, and you should still have root.

You can't flash both in the same recovery session, because SuperSU needs to set itself first and Magisk seems to get in the way if you don't boot to system first.
[Magisk] soder:
Have you used the uninstall for Magisk first? I had to do that. Then root, boot up, then hidesu I think, then Magisk.

/Söder
[Magisk] Devilix:
Yes! Finally now everythings works fine...! :)

And what about xposed 86.6? Must flash suhide and xposed?
[Magisk] Captain_Throwback:
If you want to use Xposed, you should first flash suhide, then boot up and make sure you pass SafetyNet. Then follow the procedure I mentioned here to disable suhide on the next boot. Open Magisk Manager and install the Xposed module, and reboot when prompted. Your apps should all optimize on reboot. Once booted up, you can put the suhide script back and reboot the device. Then *hopefully* everything should be working, and you should pass SafetyNet.
[Magisk] putridfoetus:
Having a heck of a time figuring out what is wrong with this mod... I'm trying to add a few files into a few different system folders, and by the logcat it appears to only be mounting some of the folders in the mod. Magisk post-fs-data system mirroring only mirrors /system/lib and 2 files in /system/xbin, so I'm wondering if for some reason my mod is making Magisk "hide" all the other folders causing phone to not boot?

Here's the post-fs-data section of the boot logcat. After this there are repeating errors about failing to load hw modules and failures to parse and set permissions for system apps.

https://github.com/putridfoetus/ViperAtmos-Magisk/blob/master/post-fs-data%20logcat.txt

Any help is appreciated!
[Magisk] Droidphilev:
Hi,

you mean there's coming a "PHH hidesu" specially for use with Magisk? I guess the "hidesu" made by PHH is not magisk ready, correct?
[Magisk] Wlkchnbndgr:
Here we go again. Safetynet Update incomming.
[Magisk] ScottIsMyName:
Update broke magisk and suhide from safetynet detection. Getting failed payload message (blue screen).
[Magisk] Wlkchnbndgr:
Same in my End.
[Magisk] elreydenj:
Correct. Thats why there was a great need for the way [MENTION=4470081]topjohnwu[/MENTION] handled the toggle of root via the manager previously. I loved SuHide but it will always be an On and Off thing. For times like this we desperately need to be able to toggle on and off.....
[Magisk] Captain_Throwback:
[MENTION=4470081]topjohnwu[/MENTION] already said that it wasn't the best solution, and that he's working on a better solution. Just because something works doesn't mean there isn't anything better ;). So if you really want the toggle, go back to the previous version. Or you can wait for the next version, however long that takes.
[Magisk] Devilix:
I have try to flash normally first xposed 86.6, then suhide, in the same recovery session... i had have only one time the "optimizing apps".

Tryed to reboot many time to see it happens... everythings ok!

And obiuvsly SafetyNet pass the test! :D

Seems to be everything ok...

All this, thanks to you!!! You deserve a beer!!! :highfive:

Nooooooo... A fu**ing SafetyNet update... :mad:
[Magisk] Brnway:
So, is your device passing or failing SafetyNet right now?
[Magisk] Devilix:
WAS pass the test... just while i was writing.... s*it...

Now we are in the same boat... :(
[Magisk] mat1jaca:
i've flashed magisk v7 and the manager v2.0, but the manager crashes when i open it. why?
[Magisk] chudy_85:
Because you don't have root!!! If you want supersu v2.78sr1 install magisk v7 then install in systemless and reboot. Now when it's boot check you have permission if you have flash magisk v7 and install magisk manager

Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
[Magisk] stefanowall:
Unfortunately, Magisk 7 doesn't work on moto x ghost: after installation, the phone boots, but then I can't even unlock the screen...
[Magisk] D4UN7L355:
Magisk v6 and systemless xposed 86.6

Does anyone know if Magisk v6 and xposed 86.6 + suhide work? Don't know if I want to make the jump but I'd like to upgrade my xposed and reflash suhide with v6.
[Magisk] JudgeDread11:
I don't use Android pay or pogo, so I honestly don't care much about safety net.

But logic tells me that a way to temporarily disable root (and xposed) and thus restoring Android to a safe environment for the duration of the use of an secure app is the only acceptable solution to have both root and pass safety net.

As long as apps can run with root permissions while passing safety net it will be a security risk and Google will always patch it.

Whether it's magisk or the root developers to implement the solution doesn't matter.

I do think that magisk is to beautiful of a project to let safety net be a issue.
[Magisk] zgfg:
And (therefore) they remain even if Magisk Manager is uninstalled - one needs to uninstall Magisk itself to clean those data.

It also includes Magisk modules and their data (if they correctly store their data to /data/adb/modules)

Hence clearing Cache, Data (from Settings, Apps) or even uninstalling Magisk Manager is of limited use in case when trying to fix issues
[Magisk] PoochyX:
This is correct

([emoji88]Chaos GSI[emoji88])