yashsingh1/xdaforums huggingface dataset:
[Magisk] Tecalote:
[MENTION=4667597]Didgeridoohan[/MENTION]

[MENTION=4470081]topjohnwu[/MENTION]

Huawei has released EMUI 9.1 based on Android P officially for some devices, and EMUI 10 based on Android Q will come soon.

As you know Huawei uses since 9.1 his new Filesystem EROFS (Extendable Read-Only File System).

I haven't rooted yet 9.1, but some Users on Android Hilfe de reported some issues by rooting EMUI 9.1.

Apps like Stock sms and Dialer would FC (force close)

No systemapps in Magisk Hide enabled, and data + cache of the apps deleted, doesn't help.

AdAway doesn't work.

I guess this is because of the new file system.

I can't provide log for the moment, due to my new job and my very limited time - but will ask the User's to get some.

I just wanted to ask if topjohnwu observe same issues on his Honor 10 View - if he got already EMUI 9.1 - and I wanted to ask if he thinks the problems with the new file system are even solvable in some time (so if he planing to fix it..)?

As always I wanna thank you for all your excellent work to keep the possibility of Root for the devices.

Thanks :good:
[Magisk] saspo59:
I think it's the opposite magisk break oos 9.05 ,oos 9.05 with out magisk works normally
[Magisk] Didgeridoohan:
Either way, without more information than the sparse pickings you've provided it's impossible to tell...

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] brown1178:
Which Magisk Version is needed for OnePlus 6 OxygenOS 9.0.8?
[Magisk] pragyan52yadav:
What is the use of link

If follow that instructions then it won't root my data slot rom

But should I try patching boot.img created by dual boot patcher?
[Magisk] BillGoss:
I had no problems with Magisk 19.3 upgrading from OOS 9.0.4 to 9.0.5 (flashed 9.0.5 then flashed 19.3). I suggest you uninstall Magisk, flash 9.0.5, check that it's ok, then flash Magisk (without any modules).
[Magisk] Paschfire:
I'm betting it the fact that there's no room left within the/System partition, having 0MB of space remaining after flashing the update.

Users are failing, or forgetting, to delete/remove System apps to regain the necessary 100MB~200MB of storage for modules requiring it.

...Just my 2cents ;)
[Magisk] guest4711:
Because modules are systemless they don't require any space on system partition... (AFAIK)
[Magisk] Artim_96:
The point of Magisk is that /system is never touched. So if you actually remove system apps, you completely break the point of Magisk
[Magisk] kondore:
So there seems to be some ****ery with magskhide on my nexus 5. In short i dont think it works

I have tried many nougat and oreo roms with clean flash every time and i still dont understand whats wrong

Uppon further attempts and many roms gone through i used a rootchecker as instructed by magiskhide troubleshoot faq to determine if magiskhide even works

I get conflictng reports between magisk and root checker. Magisk says safetynet passes, root checker says it fails. Also root checker detects root even when selected in magiskhide

I have no clue whats going on or why

.

.

Another safetynet check app passes

And another root checker detects root even tho its checked in the magiskhide list

UPDATE 1

Seems i have fixed my issue.

Dont know what exactly fixed it but im gonna type everything i did in case someone else experiences the same thing

This time before flashing another rom i wiped internal storage also. Before i was wiping everything else but keeping internal storage.

Flashed dotOs oreo rom then pico oppen gapps then magisk 17.1 instead of the latest 19

Then installed magisk manager v6 instead of v7 and repackaged it from settings to hide it.

Then checked every root checker in magiskhide and no root was detected.

I haven't updated to latest version cuz im afraid of breaking it and having to do everything from scratch again, but if my curiosity takes over i will update this post to let you know.

UPDATE 2

So i managed to install the latest magisk and manager and now the root checker detects root again even when checking it in magiskhide list so i can definitely say that the latests packages break the magiskhide functionality

I dont know if its the combination of the 2 or just one of them. i might test that tomorrow but the sure thing is that magisk 19.3 and manager 7.3.2 break magiskhide

I know magisk 17.1 and 18.1 with manager 6 works fine so next i might try magisk 18.1 and manager 7
[Magisk] brown1178:
You have to use beta or canary Magisk to make it work!
[Magisk] Didgeridoohan:
[MENTION=9301731]kondore[/MENTION] You indeed have something going on. I tested all of those root checkers and had no issues hiding root from them.

You missed an important part of my troubleshooting guide though:

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] haaffizzzz:
Is magisk 19.3 having issues with magisk hide? After updating to 19.3, the game Gigantic X detects that I have root and won't open. Haven't had this issue in 19.2. My phone is Pocophone F1 btw
[Magisk] guest4711:
On some devices switching Magisk Hide off and on again will do the game....
[Magisk] seanho12345:
I have a redmi 6 devices. Recently I updated it to andriod P. It's system-as-root. Then I flash the magisk zip. But my magisk manager is not detecting my patched img. I tried to use the recovery button combo to boot into magisk enabled system but it's still doesn's work. Any solutions to that? (it's also an A-only device BTW)
[Magisk] anonxlg:
i just found that my intel atom (x8350) tablet has TWRP and a unofficial build of lineage 13 (MM/6.0.1).

Is magisk on x86 totally different or can I use the same files/instructions to root?
[Magisk] garylawwd:
Ya just flash magisk.zip in twrp and thats it.
[Magisk] Didgeridoohan:
Nothing of note in those logs... Unfortunately I think you need to try to figure out what it is on your own. You could start by installing the Canary debug build for better logs...
[Magisk] jenslody:
[MENTION=9301731]kondore[/MENTION] and [MENTION=9761771]haaffizzzz[/MENTION] make sure the apps that detect root are not on external/adoptable storage.
[Magisk] kondore:
Seems i have fixed my issue.

Dont know what exactly fixed it but im gonna type everything i did in case someone else experiences the same thing

This time before flashing another rom i wiped internal storage also. Before i was wiping everything else but keeping internal storage.

Flashed dotOs oreo rom then pico oppen gapps then magisk 17.1 instead of the latest 19

Then installed magisk manager v6 instead of v7 and repackaged it from settings to hide it.

Then checked every root checker in magiskhide and no root was detected.

I haven't updated to latest version cuz im afraid of breaking it and having to do everything from scratch again, but if my curiosity takes over i will update this post to let you know.
[Magisk] TiTiB:
TIP for those getting the 'Magisk is not responding' error, and not being able to open Magisk Manager.

I had this happen, and tried long-press icon and chose 'Modules'. Took about 1 second, then Magisk Manager opened and performed normally.
[Magisk] martyfender:
I have 5 Nextbook Ares 8A, Intel Atom (x8350), Android 6.0.1 tablets and I run the latest Unofficial and Canary development builds, on the stock OS, with very few problems.

I however have had problems with direct install on these devices quite a few times, so I always flash in TWRP instead. I have not tested the direct install method for some time to see if this has been fixed or not, but it can take some time to fix the issues it caused, so I don't risk it.

In addition, I have had issues if I delete the dalvik cache and cache in TWRP, immediately after flashing Magisk. If I feel the need to do that, I wait until after the first boot into Android, then later reboot to recovery to do it and all is fine.

I am not sure why this happens on my devices.

Lineage? I wasn't aware, where did you get it for the Intel device, it may work for me? OT, of course, sorry.
[Magisk] Didgeridoohan:
[MENTION=9301731]kondore[/MENTION] You may simply be affected with a known bug in Magisk v19.3 where you on some devices have to toggle MagiskHide off and on at every boot.
[Magisk] wilsonhlacerda:
Yeah, I have this bug on LOS14.1.

Weird is that I've never had this problem since ancient times till v19.2. Then the bug appeared on v19.3 and is even present on v19.4 experimental buildings. :/

Something have been broken from 19.2 to 19.3.

To circumvent it I'm using the startup script to toggle Magisk Hide (only toggle once).

I hope to have that fixed.
[Magisk] I am Groot!:
[MENTION=4470081]topjohnwu[/MENTION]

Magisk won't stop checking for updates even when not allowed. MagiskHide not working for "Seeking Alpha" app surprisingly!
[Magisk] Wahyu6070:
how to compress the system folder into system.tz and make the magisk script module read it
[Magisk] TogoFire:
For me Magisk 19.3 lag apps and 19.4 brakes some functions in rom's ?

"libcoredump.so (or something like that) is usually missing"
[Magisk] jcmm11:
What, exactly, are you trying to do? And why (As in what are you hoping to accomplish)?
[Magisk] anonxlg:
No it's device specific, this isnt android_x86.

I have a problem now. Hope it's not too off topic. I tried installing riru core and it's failing to install:

- Found /system/lib/libmemtrack.so
! Can't copy /system/lib/libmemtrack.so
!Installation failed

I'd post this on a riru core thread if there were one.
[Magisk] Wahyu6070:
For pictures and questions I write here

https://wahyu6070.blogspot.com/2019/08/ask.html?m=1
[Magisk] jcmm11:
Use gzip compression. It's the only compression format you can be sure of having the decompression engine available in all cases.

tar -czf file.tgz <what you're compressing>

To decompress you have to, in the install script, extract the tar file to the temp directory then decompress it to where you want it. Exact commands would depend on exactly what you compressed. If you include the system component so you're stored files are:

./system/file1

./system/file2 etc.

Then the sequence would look something like:

unzip -o "$ZIPFILE" 'file.tgz' -d $TMPDIR >&2

tar -xf $TMPDIR/file.tgz -C $MODPATH >&2

If you want to use something other than gzip you'll need to carry your own version of busybox in the module to guarantee availability otherwise, depending on device and if you're installing via TWRP or Magisk Manager, you may or may not have things like xz available.
[Magisk] TanByv:
Issue:

Magisk modules show up in the menu and install without any errors but they don't load (MagiskCore ISN'T enabled and modules are enabled). MagiskSU works without any problems.

Device Info:

GT-I8190 (Samsung S3 Mini), Android 5.1.1, OmniROM, OmniROM Kernel (3.0.101+), No other mods, Complete fresh install with only Magisk flashed

Magisk Logs:

View attachment log.log
[Magisk] JudgeDread11:
Any modules installed?

Magisk doesn't touch the system, but modules can make part of the system with their own files which could explain missing files.

But more information would be needed to figure out what is going wrong. Device, Rom, logs etc.
[Magisk] Didgeridoohan:
Looks like it could be a script in post-fs-data.d that's causing issues. I would start looking by looking there... What modules are we talking about, by the way? If you're installing several at once, try uninstalling them all and then install them one by one to see if that makes any difference.

From the log I would guess that you're not using the debug Canary build. If my guess is correct, it would be better if you changed to that build if you can't figure things out. The logs will hopefully then be a bit more useful...
[Magisk] Wahyu6070:
where should I put the script and on where it line
[Magisk] jcmm11:
install script is part of the template and the location should be obvious when you look at that script.

https://github.com/topjohnwu/magisk-module-installer

https://topjohnwu.github.io/Magisk/guides.html
[Magisk] josmunguia:
Hello.

I need help. I can't find the option to enter to the hide list in Magisk manager. It doesn't appear. I only can toggle the option with Magisk hide but not select which apps I want to hide.

thx.
[Magisk] n0p4rk1ng:
Hi guys, I need some help about installing magisk.

I'm using Xiaomi Poco F1, and I was able to install magisk on different roms.

But on this EU Rom I wasn't. So here's what I think might cause the problem.

I forgot to disable the module that I use on the custom rom when flashing this EU rom. It might be but I'm not sure. Hopefully if anyone knows how to fix this that would be great. Thanks in advance.
[Magisk] zgfg:
Top/left, three bars, Magisk Hide - you don't have?
[Magisk] josmunguia:
No, it doesn't appear that option.
[Magisk] Octal450:
Hi

Since Android Q Beta 5, I cannot mount /system as R/W in any file browser app anymore. Can't do it from TWRP either interestingly enough.

Is it known why?

Kind Regards,

Josh
[Magisk] dope77:
Go to settings and toggle magisk hide on
[Magisk] kemkemk:
Hi. I am currently running Oreo version 20h on the Lgv20 H918 and I do not care about Android Safety Net or OTA. I need full System root on my device, however when I flash SuperSu in TWRP, it flashes as "systemless". How can I remove Magisk root and convert to full system root?
[Magisk] zgfg:
Did you see/use Uninstall option in Magisk Manager - after that, ask on SuperSU side if ypu have problems with

Btw, Magisk also provides root...
[Magisk] martyfender:
There is an unofficial, system mode version of SuperSu that I used to use in the past:

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

I'm not sure if it is compatible with Oreo, though. There are also command line options to use in the official Supersu through TWRP to force it, I believe. Why do you want system root? I've used systemless Magisk for some time now and never looked back.

Systemless is the only officially supported way to install Magisk.

https://topjohnwu.github.io/Magisk/deploy.html#system-only

According to the above documentation, system mode is currently not available.
[Magisk] mrrocketdog:
when trying to uninstall from MM i get a "failed. unsupported img" message. just what image am i suppose to use. if anyone knows?

Axon7 A2017UV2.1.OB20

p.s. tried "uninstaller" from twrp and it also failed. (forgot to get log. duh!)

now have recovery log :

https://www.dropbox.com/s/oaxhlgevr0d76su/recovery.log?dl=0

err on the side of kindness
[Magisk] mjemec:
Anyone else not passing SafetyNet all of a sudden (SafetyNet API error)?
[Magisk] Didgeridoohan:
Why do you "need" system root?

SuperSU's systemless installation has nothing to do with Magisk. That's just how rooting works on the past few Android versions (since Marshmallow or so, can't really remember). If you have issues with SuperSU, there's a specific forum for that, but you've already have those answers.

Logs will be needed...

Nope.
[Magisk] mjemec:
All good. Apparently I had issues with my mobile data connection. Everything is fine back home on wifi.
[Magisk] mrrocketdog:
logs ammended to original text. also have tried with 2 different twrp's , NFound's 3.2.1-8 and twrp 3.3.1-0

and here is log from MM ,

https://www.dropbox.com/s/43nxnk58dpbjlex/magisk_install_log_2019-08-13T093146Z.log?dl=0

err on the side of kindness
[Magisk] Didgeridoohan:
Do you have Magisk v18.1 installed? If so, try this uninstaller: https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-uninstaller-20190204.zip

If not, try the Canary uninstaller: https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/magisk-uninstaller.zip
[Magisk] khaytsus:
Why in the world would you charge the phone turned off anyway?
[Magisk] TanByv:
Hey, thanks for your reply. So, I went ahead and formatted my device and clean install the same ROM with Canary Debug Magisk and tried both installing my modules one by one and all of them at the same time.

Modules tried are: NANODROID MicroG, F-Droid and OsmAnd+ packages (Flashed with recovery) and Youtube Vanced from Magisk repo (Flashed with Magisk Manager)

None of the modules load and post-fs-data.d folder is completely empty. They flash without any errors and show up on the menu, again MagiskCore is not enabled

Here are the Canary Logs:

View attachment magisk.log
[Magisk] iDreamliner:
Thx so I go to develop option and switch the OEM bootloader on. Then flash TWRP by odin to get custom recovery installed.

Can someone confirm Magisk work on Note 5 marshmallow 6.0.1 since op stated it might not work on newer devices or with device using android 6
[Magisk] KeyzerSuze:
Hi

Is there a tasker interface for magisk, so I can root / unroot on tasker events ?
[Magisk] Ganuke2kx:
After receiving my new HTC 10 last week I " Sunshined " it ( S-off / Locked), flashed latest TWRP recovery ( and immediately created a backup / nandroid system image, data, I and boot of the 1.19 unmodified software / firmware ), then flashed 1.82 software / firmware, and lastly flashed the modified SuperSU ( then installed the latest SuperSU on to of the modified version from the Google Play Store...... And installed the previously purchased SuperSU Pro key also from the Google Play Store. ) That is the background for the state that my HTC 10 is presently at.

Then I came across this thread and it sparked my interest in giving it all a try as my next intent was to get xposed on my HTC 10...... And maybe systemless xposed would be better than the " traditional " version ?

Anyway in my thought of giving this all a try I assume I will need to fully unroot and uninstall the latest stable release of SuperSU currently on my HTC 10 ? Can that all be accomplished from within the SuperSU app ? ( Such as navigating to " settings / cleanup / " switch superuser app " AND " full unroot " ) ...... And then uninstall the SuperSU app itself ?

Is there anything more I will need to do ? ( Such as wipe / format data from TWRP recovery...... And even flash the initial 1.19 stock backup I created Or reflash the 1.82 ruu ) Before I proceed with the steps in this as well as the systemless xposed threads ?

Thanks in advance for any helpful replies that may come my way.

Ganuke
[Magisk] czarjaredv:
asus user

any updates for asus users? as it said "Some Asus devices: Asus seems to require some additional work to modify boot image.".. tried it on my zenfone2 a few weeks back and yes it ain't working... really hoping for and update... :crying::(:crying::(:crying:
[Magisk] Mrcactuseater:
Soon™
[Magisk] pirasalbe:
[MENTION=4470081]topjohnwu[/MENTION] It would be great to make Magisk Manager similar to Xposed Installer adding in the main page something to flash Magisk and the uninstaller, creating a page with the list of every mod compatible with magisk and for each element in the list the xda page, download of the zip and in case the uninstaller
[Magisk] QWEnter:
toshi127k, could you pls make a step-by-step manual/howto to make it possible to install magisk V6 on Sony Z1 compact with 14.6.A.1.236 using either TWRP or Flashtool as many other users including me are not as familiar in linux as you. As far as I understood it's not only needed to flash your modified magisk-v6k.zip but also make some changes in kernel/boot. Please attach to your post all the needed modified files as well. Thank you in advance.
[Magisk] duy0699cat:
installing on zenfone 4 problem

anyone know how to install magisk on zenfone 6? i flashed it via twrp but the twrp restarted: when i sliced a button to flash, the screen turned black and then it go to twrp main menu, nothing add on the log, seem like a crash. there's over 350 pages here and i cant find comments. if u know anything plz tell me or ask [MENTION=4470081]topjohnwu[/MENTION] to add it on the instruction.thx
[Magisk] Didgeridoohan:
From the OP:

In other words: it'll probably not work without a lot more work from someone with an Asus device.
[Magisk] trent083:
Keep getting an error when I try and use automagisk, any ideas?
[Magisk] mathy007:
Why is it that everyone is turning a blind eye on this post,i have posted here several times and nobody seems to notice it or reply it's really sad to see?
[Magisk] LeeDroid:
Have you read the error message? :-/
[Magisk] trent083:
Obviously.....what I cannot figure out is how to remove it
[Magisk] Citizen_Snips:
Wait..
[Magisk] trent083:
You know what, never mind, I didn't come here to be scorned because I don't know as much about this **** as some of you, if you cant be constructive then don't reply
[Magisk] LeeDroid:
I wasn't trolling, you just didn't art much context in your post, are you running phh SuperUser from the thread as mentioned in the error message?
[Magisk] trent083:
Yeah, looks like I might have sorted the first problem, but magisk and then automagisk didn't solve the problem I was hoping (pokemon go)
[Magisk] LeeDroid:
Do you have anything else installed I.e exposed & does a manual unmount work? PoGo is all good here, as are all other root sensitive apps
[Magisk] putridfoetus:
Are you using Xposed? SafetyNet che ks for Xposed now, so if you are, disable it in the Xposed installer, and reboot.
[Magisk] trent083:
Have been using xposed yeah, I'll give that a go
[Magisk] ACHILLES R32:
There are times that I turn off my phone and need to charge it.

Sent from my Pixel 2
[Magisk] palmbeach05:
Airplane mode? Do not disturb mode?
[Magisk] ACHILLES R32:
That works, but I know that im not the only one that's charges their phone when it's off.

Found posts of people mentioning the same problem. It's a small issue but still.

Sent from my Pixel 2
[Magisk] mrrocketdog:
[MENTION=4667597]Didgeridoohan[/MENTION] thank you very much for your help. and yes i am on v.18.1. unfortunately both .zip's you provided ended up in bootloops. i even tried restoring stock image (even though as i understand "uninstaller" is suppose to do this). thank you again.

dave

err on the side of kindness
[Magisk] Didgeridoohan:
No logs from when running either if those zips?

---------- Post added at 18:58 ---------- Previous post was at 18:48 ----------

Yeah... Seems like there's an incompatibility between Magisk and your device. It's failing miserably at restoring the selinux context for certain files at boot and that looks to be messing things up for you... Don't think there's anything you can do at the moment (possibly try a different ROM), but I'll definitely pass this on to [MENTION=4470081]topjohnwu[/MENTION]. Maybe it can be fixed, if we're lucky...
[Magisk] mrrocketdog:
sorry , making you work harder to help me. here are both logs. the one from the canary builds ended in error 1. but theyre both marked. thank you again.[emoji8]

https://www.dropbox.com/s/f5v6a2ioub0m7oc/2.recovery.log?dl=0

err on the side of kindness
[Magisk] Didgeridoohan:
I don't see anything about the February uninstaller in there, but the Canary one is displaying the same issue as the June uninstaller...
[Magisk] mrrocketdog:
and could you tell me what issue it shows? i am no good at reading logs obviously. :)

err on the side of kindnes

oh! wait , do i need to change the boot image before flashing ,? or i've missed it totally again. lol

err on the side of kindness
[Magisk] TanByv:
SELinux is actually disabled. My device doesn't have support for SELinux on Android 5+ ROMs (Original firmware only goes up to 4.1.2). May that be why Magisk can't load modules?
[Magisk] Didgeridoohan:
It's failing to use the v18.1 magiskboot tool, since the syntax is slightly different now. Instead of running the tool, it's simply displaying the available commands... The February uninstaller should work.

The uninstaller will fail if you have the stock unpatched image installed, yes.
[Magisk] MeZen81:
Any help guys app detect root and safetynet success bat response validation: fail any idea what is the problem
[Magisk] jakito:
I only get detected on the last option.
[Magisk] zgfg:
Any idea - YES

Rootbeer has been discussed here zilliom times, and the solution for UDS.

So please take your time to search back and to read about

And for Apps -disable or uninstall suspicious apps that require root, until ypu find the one that Rootbeer detects

It has been also discussed already, you can search and you will find a post where somebody pasted the source code from Rootbeer with its list of apps it looks for.

E.g., it looks for AppQuarantine