yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Does it still detect busybox if you're using the one from the Magisk repo and add Mandiri Online to the Hide list? That should hide busybox from the app (it works with, as an example, Rootbeer).
[Magisk] yochananmarqos:
I would wipe the whole thing and start over with a factory image.
[Magisk] Regys:
Are there other solutions ?
[Magisk] ultradj83:
Dears, how to manually add some files to magisk?

I need it to load 2 files in /system/etc so I copied them to /magisk/myfiles/system/etc, but this doesn't take effect.

Tks!
[Magisk] jenslody:
You need an auto_mount-file in your folder:

touch /magisk/myfiles/auto_mount
[Magisk] caeter:
Could it be that my build.prop or something blocks Netflix for me?

Because I can find Super Mario Run in the Playstore and it's known for the same behavior.
[Magisk] Paschfire:
In PlayStore Settings Menu, at the bottom does is display Certified or Uncertified? If Uncertified try clearing PlayStore app data, clear it from recents menu and rebooted the device, Once booted relaunch PlayStore check if it now displays Certified and if Netflix is now present for Download.
[Magisk] caeter:
I really have done that, but Netflixs page shows not compatible with this version and the Playstore shows Certified. I have no clue why that is so.
[Magisk] Paschfire:
Hmmm... not sure then, as mine displays the same information within DRM, expect the line "Number of open sessions" mine is showing 2, though unsure if this is of any relevance to this issue.
[Magisk] RezaRaiesi:
Hi, I have Magisk 13.2 with Magisk Manager 5.0.5 installed on my phone. I've checked the official thread of Magisk and there are new versions of Magisk Manager, but XDA labs tells me my installed version (5.0.5) is the latest version. What gives? And can I download the apk from the thread and sideload it to update Magisk Manager or should I wait for XDA labs to include it?
[Magisk] Pkt_Lnt:
Open the Magisk Manager and it should prompt you to update the app and the Manager within the Manager.
[Magisk] caeter:
I don't know what Number of open sessions exactly indicates.

But I started a help thread maybe someone can help me there.

https://xdaforums.com/oneplus-one/help/magisk-hide-device-certified-netflix-t3657429
[Magisk] shami_n:
Yes, it is factory image. I only installed TWRP 3.1.0-0
[Magisk] yochananmarqos:
No, I meant you should do a clean flash as it sounds like something is corrupt since neither TWRP nor CWM can mount /data.
[Magisk] Didgeridoohan:
I think that's something else that's going on. Like it says: for some reason your device is not compatible. Have you tried a different ROM?

If it had been the root protection kicking in, you wouldn't see the app at all or get an error when trying to install.
[Magisk] caeter:
I can see the app, because it is on my wishlist. This works also when the device isn't certified.

Another Rom could be worth a try.
[Magisk] Didgeridoohan:
Can you see the app if you search for it?
[Magisk] shami_n:
You mean clean flash of stock ROM ?
[Magisk] caeter:
No.
[Magisk] HellFish23:
I'm having very high cpu usage by a process named magisk_daemon and because of that alot of battery drain. So I tried to turn off magiskhide but it turned itself on as soon as I restart the app. Can I disable it manually?
[Magisk] Didgeridoohan:
Hm... MagiskHide should stay off. You can try disabling it manually by using this command in a terminal emulator (as su):

magiskhide --disable

But, about your issue... Have you by any chance turned off Android logging (with Kernel Adiutor or similar)? That has been known to make the magisk_daemon start using a lot of CPU. Turn logging back on and the problem should go away.
[Magisk] DAusRon:
Hi all. Can i just dirty flash magisk 13.6 beta over 13.3 stable?
[Magisk] HellFish23:
thanks! I indeed disable logging by renaming logd to logd.bin because the logd process was taking a lot of cpu too... i'll set it back and see what happens

edit: seems to be alright now, lets see if it will stay this way
[Magisk] Romullo Sousa:
Personally I have error installing ROM + GApps and Magisk ... my play services is stopping and soon after all the applications .. what can it be? WebView?
[Magisk] Thanielbracke:
can't install latest version of magisk

I have been messing around with this for a while but I cant find a way to fix this...

When I try to update magisk from v12 to v13.3 from within magisk manager I get the error "This feature will not work without permission to write external storage"

The app has all the permissions it needs so I dont understand the problem here....

I have a huawei p10 lite build nr. WAS-LX1C432B124 if that helps.

I hope someone can help..
[Magisk] kaw900r:
MagisK13.3

Just wanted to let people know that it works with DUO an app for secure login. Added DUO to hide and it doesn't flag my phone as tampered...
[Magisk] DodoGTA:
Is this a link for that app?: https://play.google.com/store/apps/details?id=com.duosecurity.duomobile
[Magisk] marcol87:
no modules

I'm on magisk 13.3 and I can't install modules.

I tried installing through recovery and got no problem but then in magisk manager there are no modules. I tried also installing through magisk manager but I got "Magisk is not activated!" error (see screenshot in attachment).

I got this problem with different versions of magisk manager (5.1.0, 5.1.1 and 5.2.0)

device: Moto g5 Plus, Android stock 7.0

(log in attachment)
[Magisk] edimonoarfa:
I'm on magisk 13.3. After installed greenify4magisk from magisk manager, magisk can't pass safetynet test. I tried to enabled greenify in magisk hide, still it failed. Need an advice for that.
[Magisk] Artim_96:
Well, adding Greenify to Magisk hide is definitely the wrong thing, you don't want to hide root and stuff from Greenify.

But maybe the module is a bit strange, I don't know what it makes wrong. I just made myself a module for that which just puts the Greenify apk into a folder in /system/priv-apps.

Maybe try for yourself, get the module template from GitHub and make it yourself, isn't hard at all
[Magisk] enzzo28:
Hey, yeah, you could, but since it's a beta over a stable version I wouldn't recommend it.

I'd uninstall Magisk first and then reflash it.

I think some modules have addon.d so you won't need to install them again.
[Magisk] rosboy:
I have had in the past issues with magisk and xposed, only thing that worked for me was to uninstall everything and reinstall magisk v12, install xposed v87 SDK23, then upgrade to magisk v13.3.

I just installed osmosis Busybox in magisk manager and it messed up my xposed. It shows installed but not activated. I cannot activate. Please see logs.

Thanks
[Magisk] TotallyAnxious:
Is it possible to symlink files from a location inside the module to a location that exists in the module? Basically I'm trying to port the Nvidia shield controller to work on aosp on the shield. I need to symlink some libs to the apk folder but I'm not sure of the correct way to do this. Could someone give me an example code or point me in the correct direction?

If it's not possible with one module, would it be possible to have a module that mounts the app and stuff first then another module after to mount the libs and to symlink them to app folder in the first module?
[Magisk] godkingofcanada:
Xposed for nougat works fine with magisk. I suggest you get a 7.1.2 ROM with SDK 25. I've never had to do anything but flash a couple of zips from recovery for xposed or magisk. Also the magisk modules almost eliminate the need for xposed. If you go with a nougat ROM like viper or xin they already have most of gravity box built into the ROM, and a theme editor, plus a lot of xposed modules have play store versions that do the same thing. Like app settings or as blockers. The more programs with modules you run the more risk of an issue. Things conflict sometimes, like if xposed and magisk have a module doing a similar task, one will interrupt the other causing slow speeds or crashing. Also, you could try setting selinux to permissive. Use an app like ROM toolbox, go to init.d and click the plus, name the file 08setperm and when you click the next box and enter

#!/system/bin/sh

setenforce 0

You can just copy and paste that. On boot your phone will set it to permissive.
[Magisk] nikhildhage001:
How to fix system could not be mounted error while flashing magisk
[Magisk] McLeige:
Hello all, I have my Magisk Manager/Magisk updated to the latest that i know of (Manager 5.1.1, Magisk 13.3)

everything works, passes safety net, root, etc.

any module i click on in the downloads section, when it shows me the readme, there is no "download & install" button on any of them, so i cant use any modules? what am i doing wrong here?

also the dark theme doesnt actually change the manager to dark theme, it just flips a switch and ... nothing.

ive tried to search this forum, along with the github issues and any other sources similar, with no luck on this issue.

EDIT: it seems the buttons are there after all, in the right part of the module box, but they are totally invisible, i am unsure why this is happening

Last Edit:

I have figured it out, substratum was somehow theming magisk and basically hiding all the buttons, it glitched on my phone so i removed it and cleared all themes, reinstalled and everything is now fixed. apologies if i have confused anybody.
[Magisk] Didgeridoohan:
Arrow on the right.
[Magisk] enzzo28:
Sup, I think it's because your partition has been mounted as read only. Maybe you chose that option the first time you used your custom recovery (TRWP I guess)

Try rebooting into recovery, and then in TRWP go to "mount menu", and uncheck "Mount system partition read-only"
[Magisk] Pkt_Lnt:
Can you post your recovery log?
[Magisk] maelset00:
Hello,

I have a sm-g930v and wanted to know if it was possible to use this method.

I know there is no custom recovery for this model, so I try to do the manipulation with ADB.

Unfortunately I'm blocked at this line of code :

adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp

With the error code :

failed to copy 'META-INF/com/google/android/update-binary' to 'common': couldn't create file: Read-only file system

Did I do anything wrong?
[Magisk] Shtiff1:
Have you tried this?

I don't think this has to do with Magisk. The Netflix app doesn't use SafetyNet or any root/tampering detecting methods other than the Play store certification.

Searching for the error message on Google shows that some users have had success with Netflix issues by renaming the file /system/lib/liboemcrypto.so to /system/lib/liboemcrypto.so.bak. I have no idea what that does, so if you want to play with that make sure to have a backup and I'd also do some research first... Over and out.
[Magisk] Didgeridoohan:
Are you using an up to date version of ADB?

You could try pushing the files and folders one by one:

adb push META-INF/com/google/android/update-binary /data/local/tmp
adb push common /data/local/tmp
adb push magisk_inject /data/local/tmp
adb push boot.img /data/local/tmp

And remember that any version prior to Magisk v13.6 won't work for this.

Edit:

If the above doesn't work, try adding the common and magisk_inject folders to the path:

adb push common /data/local/tmp/common
adb push magisk_inject /data/local/tmp/magisk_inject
[Magisk] Shtiff1:
Sorry to bother or if off topic. I'm trying to find out how you link post like this one I quoted you on, or how to link any post or word like "this".
[Magisk] Didgeridoohan:
Nice copy-pasta...

Yep, a bit off topic... But, just so you won't rip quotes completely out of context and make them look like your text again (like above), here are some tips (I'm only talking about the web-based forum here, no apps. I don't use 'em):

Just paste the link into your post and you're good to go. If you want to make a word into a link you encapsulate it in the url-tags, like so:

[URL="http://www.thisisalinksomwhere.com"]this[/URL]

There's a button like a small chain that'll do it for you, right above the text box (select the text, press the button, follow instructions).

Every post in a thread has a number above it. This is a direct link to the post and a useful way of pointing to specific posts.

If you want to quote someone from another thread, there's a useful thing you can do. Each post has a button under it named "Multi-quote" (or just a single quotation mark on small screens). Press that, go to the thread you wan't to post in and reply/add new post. Underneath you'll see a text about having selected another post not part of the thread and an option to quote that as well (or deselect it). Can be quite handy...
[Magisk] Shtiff1:
Lol, yah that's why I was asking and I saw you do it Alot. I'll try them out. Much easier on computer, I'm using XDA Labs. Still laughing. Lol. Thank you
[Magisk] DAusRon:
Anyone facing systemless hosts toggle in magisk manager doesn't keep its settings? I turned on the toggle, then after re-open manager, the toggle turned back to off. But, it works since the magisk log shows *enabling systemless hosts file support* and *bind_mount: /magisk/.core/hosts ->/system/etc/hosts*

ps: I've clean flashed Magisk 13.6 beta (uninstall 13.3 stable using latest uninstaller zip and flash 13.6 beta through recovery). I also flash Unified Hosts Adblocker 2.7 through manager). UHA 2.7 hosts file generated at magisk/.core/hosts is correctly installed with ~1.17 MB, even after a reboot. Just the toggler in Magisk Manager 5.2

Thanks
[Magisk] Thanielbracke:
Just bumping my issue here hoping someone can help me...
[Magisk] enzzo28:
Have you checked that is not a TRWP problem related? I mean it could be caused because your partition has been mounted as read only.

Try rebooting into recovery, and then in TRWP go to "mount menu", and uncheck "Mount system partition read-only"

Just guessing...
[Magisk] Thanielbracke:
I checked that. It was already unchecked so that schouldnt be the problem...
[Magisk] Didgeridoohan:
Yeah... Sorry about that. I don't think I was quite awake when posting that... :D (it was at 2:30 am for me)

I hadn't added the "common" and "magisk_inject" folders to the paths, but I fixed the original post now. Try again, and thanks.

Edit: Well, actually... It should work anyway. I wouldn't be surprised if that's just another Samsung quirk.

Edit 2: Also make sure you're on the latest version of ADB.
[Magisk] jenslody:
From your quote

and

the error occours obviously, because adb pushes single files instead of the whole folder as you expect.

On my Fedora system it works correctly, that means it pushes the whole "magisk_inject"-folder.

As @Didgeridoohan wrote: make sure your adb is uptodate.
[Magisk] maelset00:
Hey, another small question.

So I have my boot.img file (thanks [MENTION=4667597]Didgeridoohan[/MENTION]).

I've to flash it on my Galaxy s7 (Verizon).

I converted it to tar.md5 file to use it with Odin, so I put the file in AP, I started the process but when the smartphone restarted, no root (I had to manually install the Magisk Manager).

There's another way to flash it?

I tried with the Fastboot but my smartphone was not recognized with "fastboot devices", so I think that the fastboot did not exist on this device.
[Magisk] Didgeridoohan:
I don't think you have fastboot on Samsung devices, so Odin would be the way to go.

Does the Manager report that there's no Magisk installed, or is it just root? If you could grab a logcat from boot that'd be great. Power off your device, execute the following commands and start it up:

adb logcat -c
adb logcat > no-root.txt

When the device has booted, wait a little bit and then press CTRL+C to finish the log. The file will be in whatever directory you were in in the terminal when starting the logcat. Attach that to a post here and maybe we can find something... If you could upload the generated new-boot.img file as well that'd be good.
[Magisk] maelset00:
I found that I now had a problem with my setting menu and with my sim card.

The setting menu is different and has duplicate options.

My sim card this time says "Roaming indicator off".

Screenshots (I can't post links) :

i.imgur.com/5GrkQtf.png

I think I will reinstall the rom stock.

PS: I try to have the logs but when I run the command, it puts me waiting for my device but when it detects it, it runs and goes directly to the second command where it puts me "access refused "
[Magisk] Didgeridoohan:
Could you copy and upload the enitre output from when you're running the adb commands to generate the new-boot.img?

Sounds like you ran the two commands toghether... They should be run one at a time. But anyway, I'm not thinking clearly today... You don't need to run "adb logcat -c" when catching a logcat from boot. Just run "adb logcat > no-root.txt" and nothing else.
[Magisk] willkof2:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION] and [MENTION=8340552]jenslody[/MENTION] for the quick reply, I installed the latest ADB and now gave a different error :(

Microsoft Windows [versão 10.0.15063]

(c) 2017 Microsoft Corporation. Todos os direitos reservados.

C:\WINDOWS\system32>cd C:\Users\Luana\Downloads\Magisk-v13.6(1360)

C:\Users\Luana\Downloads\Magisk-v13.6(1360)>adb shell "rm -rf /data/local/tmp/*"

C:\Users\Luana\Downloads\Magisk-v13.6(1360)>adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp

META-INF/com/google/android/update-bin...ed. 4.0 MB/s (4728938 bytes in 1.142s)

common\: 4 files pushed. 3.7 MB/s (3324183 bytes in 0.859s)

magisk_inject\: 2 files pushed. 3.7 MB/s (364888 bytes in 0.094s)

boot.img: 1 file pushed. 5.1 MB/s (3504046165 bytes in 661.232s)

8 files pushed. 5.0 MB/s (3512464174 bytes in 663.374s)

C:\Users\Luana\Downloads\Magisk-v13.6(1360)>adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"

- Unpacking boot image

MagiskBoot v13.6(1360) (by topjohnwu) - Boot Image Modification Tool

mmap failed with 12: Out of memory

! Unable to unpack boot image

C:\Users\Luana\Downloads\Magisk-v13.6(1360)>
[Magisk] maelset00:
Still complicated with Samsung...

Finally, here are the logs of the creation of the file new-boot.img:

gist.github.com/33f55abf3e935df401dcc88abff00a8c

For once, everything works perfectly for the moment.

So I converted the new boot.img file to tar.md5 for odin.

But since I do not have any luck, I come to an error with odin ...

Here are the logs

gist.github.com/a70178396644ea4e779d09149746a591

(PS: I know, I am redundant and thank you all for helping me;))
[Magisk] MisiekDP:
I flashed Magisk v12.0 to Nougat (dual ROM using DualBoot Patcher) and no root :/

Anyone can help me?
[Magisk] DodoGTA:
Please clean install Magisk Manager v4.3.3: https://github.com/topjohnwu/MagiskManager/releases/download/v4.3.3/MagiskManager-v4.3.3.apk
[Magisk] Didgeridoohan:
That's progress at least... I don't have anything to add unfortunately. I'll put it on the to-do list...

No worries... It's great to see someone testing out the new ADB installation process. It's still in the beta branch, so hopefully this'll help getting it nice and stable.

I don't do Samsung, so unfortunately I can't help with the whole Odin thing. Hopefully someone that does use Samsung ([MENTION=8340552]jenslody[/MENTION] :p) know more.

From the Manager screenshot it looks like you do have root... Is it only Titanium Backup that doesn't recognise it? Any specific reason why you're using v12 and not an up to date version of Magisk? If it's not working (for whatever reason), have you tried the current beta?
[Magisk] MisiekDP:
With v13 and up Magisk isn't compatible with DualBoot Patcher :/

Only version v12 and below works with DBP app.
[Magisk] Didgeridoohan:
Ok... Try this Magisk module. It'll symlink the su location to a more standard one. Might work...
[Magisk] MisiekDP:
Thanks! Working :)

---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------

Magisk v12 with Manager 4.3.3 works :)
[Magisk] caeter:
Thanks, I try that!
[Magisk] jenslody:
How did you convert the image ?

I just used Odin to flash my newly created boot.tar.md5 without any issues.

No issues while flashing, but only a partly working root, but this is another thing:

I had to install MagiskManager manually, and can not install modules, because "/data/magisk" is missing.

It's not part of the boot.img and is normally installed directly into /data while flashing.

I think the magisk-binary should set it up, if it does not exist on start.

I will give feedback to [MENTION=4470081]topjohnwu[/MENTION] directly about this issue.
[Magisk] JonathanRAZ:
I have same issue it only worked one time for me maybe xposed messed up magisk

NOTE:disable xposed reboot and try again for me it works without xposed enabled
[Magisk] JonathanRAZ:
[MENTION=7617539]anshsharma123[/MENTION]
[Magisk] buayasawah:
Is there any difference between manually flashing the zip via twrp with flashing via xposed apk?

Edit : ive tried flashing via xposed material design and the result is still the same

Can someone help?
[Magisk] anshsharma123:
I tried that earlier and it worked! But it should work with systemless xposed too! Coz its supposed too!
[Magisk] JonathanRAZ:
Yeah i know lets see if someone else or OP says something
[Magisk] anshsharma123:
Exactly!
[Magisk] Captain_Throwback:
There seem to be a LOT of people reporting issues currently. I want to remind everyone that they should be reading the OP prior to posting about any issues, to ensure they've installed everything properly. Additionally, please see the quote from the OP below, to "remember" how to troubleshoot issues with Magisk.

I'd also recommend pulling a logcat if your device has issues while in Android with root or SELinux, or when booting up after flashing Magisk. EDIT: Additionally, a recovery log of the flashing process from TWRP might be helpful to identify issues with the boot.img patching.

If you want to know why your post is being ignored, and you haven't done the above, then now you know ;). If you have posted an issue and included the proper logs and/or boot.img (if applicable) and haven't yet gotten a response, please be patient. [MENTION=4470081]topjohnwu[/MENTION] is only one person, and has a real life that also keeps him busy.

P.S. Maybe someone can create a separate thread for the people trying to get Pokemon Go working, with a guide? All of those posts are just cluttering this Development thread, making it difficult to sort out the real issues and work on actually improving this awesome tool.
[Magisk] buayasawah:
Well despite exposed systemless isnt activated on my device, i still can log in. Weird.

Hopefully the dev can get it work :(
[Magisk] gk1984:
Get rid of the SuperSU app too. Use the phh.su app linked in the 2nd post.
[Magisk] GXGOW:
Well it was removed too. But help is no longer needed. I was trying to get the new Pokémon Go to work, but apparently disabling Xposed and unmounting SuperSU was al that's needed to get it to work. I'll just wait for the next Magisk update to switch to phh.

Thanks for the help anyway! :D
[Magisk] tasstass99:
Can't get it to work i've got an lg g4 with Imperium Rom V5.0 http://xdaforums.com/g4/development/rom-imperium-rom-g4-v1-0-t3312337. I unrooted it via supersu and deleted all files needed (didn't find any files though). So my problem is it wont boot as it loops on when I start it and doesn't even go to boot animation just boot logo.
[Magisk] The_Kian:
I uninstalled my superSU, installed magisk and installed phh root and magisk says root status is mounted. I can't toggle anything off and i can't install the phh app. What did i miss?
[Magisk] _M4rc05_:
Parse Error - There is a Problem Parsing the Package

Hi, excuse me, I have had a problem with installing the Manager apk, in my old samsung galaxy grand prime (4.4.4).

The error is:

Parse Error - There is a Problem Parsing the Package

I tried the solutions offered by Mr. Google, but do not give results.

Is it possible to fix it?

Thanks!
[Magisk] Devilix:
Somebody know if magisk works with Cyanogenmod 12.1 nightlies for sm-n9005?

I think to make all right, but when i switch toggle for remove root, it switch back in 0.5 seconds... :( What is wrong???