yashsingh1/xdaforums huggingface dataset:
[Magisk] _u2pop_:
Hi my device was rooted with superSU by chainfire and i full unroot on supersu setting then i installed/flashed via TWRP magiskzip phhsuperuserzip xposedsdk23zip then install from play store phhsuperuser and final install magisk manager and dont get success when i opened it look the error i get please somebody can give me a tips for fix it? Im using a samsung galaxy s7 edge, thanks

Sent From My Samsung Galaxy S7 Edge Duos SM-G935FD
[Magisk] JudgeDread11:
You can find a ready made module to run action launcher as a system app systemless in the collection of magisk modules thread.
[Magisk] GrischaK:
Hello,

it would be great, if someone could write in the Magisk FAQ, what is the problem, when Root toggle switches back. I had it worked and now I flashed again and again the

necessary files and I am failed twice.

I have now tried your attached zip file and I don't understand is this also a version for phhSU oder SuperSu from chainfire?

For my phone it shows the "slow "Optimizing Applications..."," at the first Boot after flashing magisk and the newer su bin. But again Root Toggle can't be switched off ;-(
[Magisk] zzzhead:
You probably have pre rooted binaries at

/supersu

/system/bin/su

/system/xbin/su
[Magisk] The_tomorrow_person:
I don't know why it isn't working

Hi, I have a OnePlus 3, which I unrooted from inside SuperSU and uninstalled Xposed from TWRP. Then I installed Magisk after that, SuperSU & Xposed. But I can't seem to get it to work. What did I do wrong? :(

I'm trying to install this because I wanna use Pokémon Go (0.37.0) on my rooted phone and on the previous version it loads up quickly but when I install the update it's stuck on the loading screen. Please help!

Have a OnePlus 3 ONEPLUS A3003

SuperSU ( 2.78 )

TWRP 3.0.2-0

Rom : OxygenOS (3.2.4)

Unlocked Blootloader

https://imgur.com/a/wZAdH
[Magisk] Ramzh:
Try this:
[Magisk] GrischaK:
Hello,

thanks for your help,

Could you explain me, what pre rooted binaries means and what I have to do?

I have tried deleted xbin/su and I didnt find su in /bin/

I am using resurrection remix custom rom for samsung s4 and I have flashed it yesterday to the newest version and didn't want flash it again so fast, but I want to play Pokemon .

I don't find the directory /superuser.

Root Toggle worked yesterday, but not now.

[MENTION=6855042]Ramzh[/MENTION]

I have tried this.

Thanks
[Magisk] The_Kian:
Quick question. I heard this doesn't work with certain roms that have built in root. Is chroma one of these and is there a way to make it work.

I wanna play Pokemon Go when the update arrives :D
[Magisk] ming86:
The zip file is phh's SU, the only different is the su binary is latest phh version.

For my case, from the magisk log file, sometime magisk doesn't mount su root, thus superuser and Xposed won't work. reboot phone likely fix the error, but have to wait a long slow "Optimizing Applications..." again.
[Magisk] Jeggu:
Has anyone tried magisk with cm14? You'd have to remove the preinstalled root binaries but would safetynet pass after that?
[Magisk] lancespahr:
I know Xposed works for my phone, as I used official Xposed ever since I first rooted. I'll try reflashing the stock system RUU and going from there.. I'm on stock but wouldn't surprise me if something got wonky while flashing stuff
[Magisk] Olympus593:
Hi, I'm having a problem with camera on my Nexus 5 on latest Santhosh AOSP 7.0 Nougat.

Magisk works flawlessly, but the Camera doesn't work in any app. Most of them crash or give the "Can't connect to Camera" error, some only show a blank screen.

I noticed that the camera works if SELinux is turned off, and also if Magisk is uninstalled. Searching this thread, found that it could be some permission stuff, but the uninstall/reinstall procedure doesn't work and TWRP 3.0.2-0 doesn't have the Fix Permissions button anymore.

Is there another fix or procedure? The camera should work with SELinux turned On, right?
[Magisk] Toronadian:
I also have a zenfone 2 but I have not unlocked my boatloader. I was wondering if this works if I were to install this using just a tethered CWM custom recovery? How I rooted my zenfone 2 has always been to use the tethered recovery and that's it.
[Magisk] Turbopuschel:
Seems to be a general issue for Xperia (Zx ?) users. I have the Z1 compact and are experiencing the same issue with stock ROM. BUT doing this from Resurrection Remix ROM (Marshmallow) worked. So somehow Sony stock ROMs seem to hinder this. Or ist it Lollipop? Because that is the newest stock ROM for me. But I saw a Z3 user having this issue and they have access to a Marshmallow stock ROM.
[Magisk] zakijesk:
i must have done something wrong because ota update failed

deactivated xposed reboot then i toggled off root in Magisk Manager ?

can twrp cause this ?

ps. pokemon go works ?
[Magisk] iFedix:
there's an xposed systemless version! The dev told me that it works! http://www.miui.com/thread-4859968-1-1.html

Let me know!
[Magisk] FabioSan:
Thank you SIR :)

Now on my OnePlus X I can continue to Play Pokémon GO :)
[Magisk] tota123:
Do i have to use stock rom

I am currently using cm 13, so to use this do i have to use stock rom can't i use on cm?
[Magisk] redrivera:
That actually makes sense to me. I'll try that out right now.
[Magisk] oldwolf613:
Since the TiBu dev himself recognizes a potential issue & sees fit to include a pop-up abt it on initial app startup, the fact that you ignore warnings & never had problems only fulfills the expression "your mileage may vary".

I'm only interested in finding a solution. Please consider that just bc I don't have experience in adb & am not ashamed to admit I have limited experience in that doesn't mean I don't know or appreciate other tech issues like general troubleshooting considerations. I used to teach computer networking classes for Novell in their education channel, as a certified instructor; & taught their Service & Support (troubleshooting) class many times - so please feel free to mention specific solutions beyond your potentially unique experience, or circumstantial card size things you heard about.

Not having evidence of probs is not proof against other's experience & I will openly thank & praise anyone who can find a solution I can use. I welcome constructive input fm anyone.

---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------

FWIW, I did err in not using my sig w/all my phone's details. My card is a SanDisk 128Gb, not 32Gb & the phone supports, theoretically 2Tb even tho none that big are made.

In terms of the ROM, it is stock.
[Magisk] m0han:
hi [MENTION=4667597]Didgeridoohan[/MENTION] and others. apologies if this is not the place and if this has been addressed here before. busybox 1.27.1 by YDS does not install correctly for me with magisk v13.3. so, i can't get mybackup pro app to run. any help would be appreciated. thanks.
[Magisk] Didgeridoohan:
Don't know about YDS... Never used it.

I always recommend [MENTION=4544860]osm0sis[/MENTION] busybox. Works great and installs as a Magisk module. Currently you have to flash it in recovery, but he's working on making it flashable in the Manager. You'll find it in his Odds and Ends thread.
[Magisk] mark manning:
This basically sums up everything I needed to say.

Thread cleaned of the lucky patcher conversation
[Magisk] Rom:
Ok, in your log i see this:

"E( 221: 236) mount /dev/block/loop0->/dev/source failed with 22: Invalid argument"

For me its looks like an partition incompatibility with Magisk script installation, provide an loggcat if you can.
[Magisk] CaptPetrenko:
Magisk issue on Moto G5 Plus

So I updated Magisk to the latest version 13.3. And there is a problem with magisk.img mounting. Log file is attached
[Magisk] culiacanazo:
*chuckles*

???

---------- Post added at 09:05 AM ---------- Previous post was at 09:03 AM ----------

Still here... In case XDA discontinued it's thumping beat
[Magisk] tag68:
Idea what could cause the problem: On Moto Z Play Lenovo fixed the f2fs issue with some firmware update, but somehow the resulting loopback device got read only. If they do something on Moto Z Play, it may behave similar on Moto G5 Plus.
[Magisk] n.p.:
Can't do that. When I navigate to the folder, "Use the current folder" is grayed out, and I can't select it.
[Magisk] kavee.gauravjoshi:
Is there any impact on functioning of Magisk in case of:

1. Clean flashing ROMs pre-rooted with Magisk

2. Dirty flashing ROMs pre-rooted with Magisk

Can dirty flashing of ROM cause an issue with Magisk? The previous issue i faced was resolved when i clean flashed my ROM which is pre-rooted with Magisk

As far as I know, in both the above cases - one needs to install Magisk from scratch once the ROM is flashed (dirty or clean) i.e.

* uninstall pre-installed Magisk by flashing latest Magisk uninstaller zip in TWRP

* install Magisk by flashing latest Magisk zip in TWRP

Just wanted get confirmation / information from the expert users, hence posting this question here. Thanks.
[Magisk] Didgeridoohan:
Well, it depends. If the installation zip simply flashes the Magisk zip at the end, there shouldn't be any issues. Of course, issues could arise if the integrated Magisk version is older than the one you currently have installed. But even then there shouldn't be too much issues since the installation script will restore the stock ramdisk and repatch it for the new installation. The Manager will still be the newer version though, since an older version won't be installed over it. That could cause issues if the ROM version of Magisk is older than the Manager supports. And if the ROM creator has the Magisk Manager pre-installed as a system app I guess it could cause issues as well... Pre-installing the Manager isn't necessary since v13.1 though, since it's bundled in the installation zip.

I don't deal with pre-rooted ROMs myself, but if the ROM creator does it properly (just flashing the zip at the end), you shouldn't have to uninstall anything after a flash (clean or dirty). Just run the Manager and let it update. Or flash in TWRP.
[Magisk] chowchillacharlie:
Hello folks,

I have latest Magisk installed on my OP3T (latest open beta) and i can get android pay and netflix to work but My EE (mobile network app) and my Halifax Banking app both say my device is rooted.

Any suggestions?
[Magisk] sweeney_uk:
Have you tried selecting them in magisk hide? I have to do that to get My EE to work.
[Magisk] chowchillacharlie:
Silly me, yeah. that worked. had to wipe the data from my Halifax app to get it to work but all is good now.

Thanks.
[Magisk] kwanthenewbie:
I heard that Xposed Magisk module anyway not compatible with Magisk right?
[Magisk] teddy0209:
If you're talking about the sdk25 xposed, then I don't think this is the right place to ask... You could just try it, or ask in their respective xposed thread...
[Magisk] aleMarvel:
magisk 13.3

note 4 snapdragon

miui eur version (xiaomi.eu_multi_HMNote4X_7.7.20_v8-7.0)

don't pass safety net.. and viper don't work too.. i tried all..

universal-safetynet-fix-v1.10.1

universal-safetynet-fix-v2-beta-4

v4afx_v1.4

ViPER4Android-master

nothing.. what is the problem ? magisk is not compatibile with miui eu ?
[Magisk] nzube14:
My first attempt at a logcat, forgive me!

Logcat
[Magisk] DodoGTA:
Magisk Hide doesn't work with MIUI
[Magisk] Recycool:
Samsung Galaxy S5 plus - G901F - LineageOS 14.1. Magisk have been fixed by the time dev on last version (26-07-2017) no longer bootloop.
[Magisk] :
Please need help with continuous manager fc. I'm getting this error:

07-26 10:34:01.308 E/SPPClientService(8948): [PackageInfoChangeReceiver] [handlePkgRemovedEvent] PackageName : com.topjohnwu.magisk, true, false

07-26 10:34:02.873 E/SQLiteDatabase(5773): Error inserting pkgname=com.topjohnwu.magisk selected=true
[Magisk] danilo_scala:
where i find the last version 26/07/2017? i will try in my xperia z5 premium
[Magisk] sanguine13:
Hi. I've just installed Magisk 13.3 on Samsung Galaxy S7 with Nougat. For me Magisk works perfectly, with no problem hiddind root from apps.

Great Job!!!

But I have one question. SuperSu by Chainfire has an option called "Force user" which give an opportunity to use specific app as system app (or system user - I don't know). Is it possible to do such thing with Magisk? I have one app which need to be started with forced system user or it will freeze and than restart phone.
[Magisk] Recycool:
Never mind, I did a clean install and it isn't working again.

Your update should arrive through OTA (settings -> about device -> updates.)
[Magisk] Artim_96:
Deleted

Never mind...
[Magisk] DodoGTA:
Please give a screenshot of that option
[Magisk] farhan76242:
Guys I am installing Magisk Module after download and install then I reboot my phone but still Magisk module section says Module will be update at next reboot whenever after installed I already few time rebooted and shutdown my LG G5 Fulmics 3.5,

Have you any idea how can I fix this problem???
[Magisk] sanguine13:
Here you are :)
[Magisk] viking_kong16:
Dolby atmos doesn't seem to work on latest magisk 13.3..how to have it back?
[Magisk] Shtiff1:
If I install busybox, will it mess up magisk? Or fail SN?
[Magisk] jenslody:
It's a known issue with (some ?) Samsung devices, see my post.

You either have to flash the modules through TWRP or use a modified version.

I have created zip-files for for F-Droid Privileged Extension, Unified Hosts Adblock and Magisk FolderMount with slightly modified update-binary.

F-Droid Privileged Extension 7-13-2017

Unified Hosts Adblock v2.2

and Magisk FolderMount v0.8.7 attached to this post.

The zips are all unsigned.

The only modification is in update-binary, because Samsung forbids starting of processes below the /data-folder and we need to use the magisk-binary without prepended absolute path to "/data/magisk".

I therefore removed this path for all calls of the magisk binary, so from inside MagiskManager the script uses the magisk in system-path ( "/sbin/magisk" on my J5 ) and for flashing from recovery I prepended the "/data/magisk"-folder to the actual PATH-variable.

With this modification the script works from TWRP and MagiskManager without the need to modify Magisks "util_functions.sh"-script.
[Magisk] Shtiff1:
Deleted
[Magisk] MasterOran:
Hey guys,

i graped an old device with 4..1.1. (ionk tp8-1200qc).

Does Magisk work on thoose old systems? As i have no Stock rom above 4.1.1.

Can someone point me out a solution wich whould result into a systemless device in the end?

Thanks i advance
[Magisk] Pkt_Lnt:
Check the title of the main thread, a sticky in the Magisk forum. It says 5.0+ and above.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

I see nothing in the Magisk forum that has anyone trying a 4.0 version, but you could search it.

https://xdaforums.com/apps/magisk
[Magisk] dony71:
does magisk support android TV 6.0.1 pure nexus ROM?

i'm using this rom

https://xdaforums.com/nexus-player/development/rom-pure-nexus-t3271236

i try installing magisk and find out SU root is working but cannot get magiskhide and safetynet check pass.

anybody has experience?

---------- Post added at 03:09 AM ---------- Previous post was at 02:49 AM ----------

found this, it seems magisk hide not working on ADT-1 running android tv pure nexux 6.0.1 ?
[Magisk] ferryry:
Magisk installed, but no magisk

Error: Magisk installed, but no magisk

Device: Lenovo P70; ROM: Unofficial LOS v13.0

What i've done:

-Reboot many times, still no magisk

-Uninstall magisk --> uninstalled, install again --> still no magisk

-Clear cache and even data, still no magisk

i still can't insert any link or attach any file cuz i'm new here so i can't show logcat and recovery log. Any suggestion for that?

I'm sorry but that's the only thing i can provide. Rly appreciate if there is someone who can help me
[Magisk] Shtiff1:
Is this crash of anything significant?

XT1254, 6.0.1, STOCK ROM

--------- beginning of crash

07-25 22:13:44.028 334 406 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=10926 ns=mnt:[4026545289])

07-25 22:13:48.301 334 406 I Magisk : proc_monitor: com.adt.pulse (PID=11221 ns=mnt:[4026545254])

07-25 22:13:53.163 334 406 I Magisk : proc_monitor: com.google.android.apps.paidtasks (PID=11617 ns=mnt:[4026545253])

07-25 22:15:04.748 334 406 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=14147 ns=mnt:[4026545272])

07-26 01:48:48.944 334 406 I Magisk : proc_monitor: com.google.android.apps.paidtasks (PID=5508 ns=mnt:[4026545341])

07-26 03:03:27.461 334 406 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=9516 ns=mnt:[4026545349])

07-26 07:49:09.278 334 406 I Magisk : proc_monitor: com.google.android.apps.paidtasks (PID=11324 ns=mnt:[4026545357])

07-26 08:18:18.444 334 406 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=12571 ns=mnt:[4026545311])

07-26 13:49:12.017 334 406 I Magisk : proc_monitor: com.google.android.apps.paidtasks (PID=25655 ns=mnt:[4026545273])
[Magisk] kavee.gauravjoshi:
Thanks for the reply :)

I tried both - dirty flash and clean flash. My ROM just flashes Magisk zip at the end. Magisk gets installed fine in both the cases, but modules give issue in case of dirty flashing. I couldn't flash any modules in case of dirty flashing (the same one's were working perfectly fine before the dirty flash). However there was no such problem in case of clean flash. Same module zips got installed absolutely fine.

Sorry i couldn't get any logs for module installations but recovery logs would be similar to ones i shared last time.

Previous recovery log: https://www.dropbox.com/s/hm05ez0rrxtycvj/recovery old.log?dl=0

The one thing that i do remember is during dirty flashing, there was additional flashing message for addon.d.

************************

* Magisk v13.2 addon.d

************************

This part doesn't appear on screen in case of normal magisk installation or during clean flash. Also, i think there was a message related with boot image.

I will try to get logs next time. But personally will be clean flashing every time to avoid any issues.

Just wanted to share my experience to see if clean or dirty flashing causing issues for Magisk modules.
[Magisk] Forever Alone:
root pop up does not come ..
[Magisk] Didgeridoohan:
If you haven't already, look through the MagiskHide part of the troubleshooting guide. Might be something there you can use.

Depends... Is everything working as it should? If so I'd say it's not very significant. :D

Ah... The addon.d thingy-mah-bob.

I've seen reports that it's not quite functioning as it should all the time. That may very well be the source of your issues.

I can't give any advice on that though, since I've never tested it myself. Gonna have to load up a ROM with it and test...

Details? Logs? Anything? :confused:
[Magisk] Shtiff1:
Yes everything is working good. Thnx
[Magisk] teddy0209:
As the previous reply to you, magiskhide on v13 doesn't work on miui, but using the module snfix it should work if you're using the test versions, just head to the snfix threads OP... You'll see there what you need to do...
[Magisk] kavee.gauravjoshi:
No problem, just let me know if you want me to test the above and generate logs for you. Let me know scenarios / steps to follow. Thanks. Cheers :D
[Magisk] Mangetsu:
Hello.

Can't install Magisk 13.3 - Magisk image mount failed.

Note 4 N910C, RAM - eRobot, tried with different kernels including stock one.

What can I do?
[Magisk] C y a n i d e ~:
Magisk v13.3.zip giving a "boot image patched by other programs" error even tho I'm on a fresh stock rom. (magisk-uninstaller gives the same error :confused: )

But I can install Magisk v12 perfectly fine (the problem is I can't update to latest magisk) :confused:

I attached the recovery.log
[Magisk] Didgeridoohan:
Yeah... It's the addon.d script clashing with the pre-rooted ROM. Bot the ROM-include zip and the Magisk addon.d script get run at the same time. :silly: That's what's showing in your log as well.

I honestly don't get pre-rooted ROMs... It just complicates things.

Anyway... Until either the ROM developer leaves out the Magisk zip from the ROM or [MENTION=4470081]topjohnwu[/MENTION] updates the addon.d script you can get around the issue by flashing Magisk manually after an update. Kind of defeats the purpose of an addon.d script, but what you gonna do? :laugh:

More than one user has reported this... So, all you really can do is wait for a Magisk update that fixes it.

Although, if you don't mind getting your hands dirty there are a couple of users that have reported using old update-binary scripts from the beta releases to get around the issue. You could give that a try... But you'll be pretty much on your own support-wise.

That recovery log shows something else than a stock ROM... Take a look in the troubleshooting guide under "Boot image patched by other programs".
[Magisk] JohnCorleone:
Well I decided that if I was going to start over again for a little update on my HTC 10, I was going to try and push my luck. So, I flashed The modified aboot with the red text removed, manually overwrote the YouTube.apk in the System /app folder and fixed the permissions, then I tried that Substratum and blacked out a bunch of apps... And I am still passing the Safety Net check! I have been skimming through the comments...what is the best way for me to get Busybox installed without messing up the Safety Net or is leaving the Busybox alone and not using ROM Toolbox Pro the only solution right now? Thanks
[Magisk] Didgeridoohan:
Busybox - [MENTION=4544860]osm0sis[/MENTION] Busybox installer. Flash in recovery and it'll be installed as a Magisk module (Magisk Hide can hide it). He's in the process of updating it to Busybox version 1.27.1 and at the same time updating the zip to be able to be flashed in the Magisk Manager. Just keep an eye on his thread. Edit: It might be released this weekend or early next week. Source: https://xdaforums.com/showthread.php?t=2239421&p=73172977#post73172977

ROM Toolbox Pro - No idea... I guess it depends on what you do with it.

System modifications in themselves doesn't trigger SafteyNet.
[Magisk] JohnCorleone:
I just decided to go for it with osmOsis 1.26.1 all zip and I am still good! I am not going to push it with any of the modules ...at least until I make a backup! Thanks for the quick response and I will be looking for the osmOsis update!
[Magisk] MasterOran:
Thank you for ur reply.

Well I noticed the 5.0+ thtas why I asked here. Maybe there was a old version which works with 4.x as well.
[Magisk] sancamcal:
Hi all,

i have one problem with Netflix. I have a j5 2016 with RR 5.8.3 , i have latest version of Magisk, 13.3 and pass SafetyNet with fix module. I can download Netflix from Play Store, run but when i try to play any content it gives me this error "There is a problem playing the video. Please try again. (2.101)". I have tip in Magisk hide for Netflix, Play Store and Play Services, i have uninstall Netflix, delete data from Play Store, check that i appear as Certificate in Play Store.. Someone know what could happens?
[Magisk] n.p.:
I am going to guess (after a lot more research) that your TF card is "adoptive storage" rather than "portable storage" (mine is the latter).

That likely makes this a lot more difficult to overcome.
[Magisk] C y a n i d e ~:
Yep done that already, I even took the boot.img from the manufacturer to make sure I got the stock boot.img.
[Magisk] Didgeridoohan:
In that case I'd guess the manufacturer is using a non-standard boot image... Or something along those lines. When installing, there's simply a check if there are no patches in the boot image, if there are Magisk patches in the boot image or if there are other patches in the boot image. In your case it triggers on "other".

Open a GitHub issue with details on the issue, the recovery log and a copy of the troublesome boot image.