yashsingh1/xdaforums huggingface dataset:
[Magisk] williamlaw:
Just tried to flash with below procedure but failure to get root. Please advice.

Using AOSP 7.1 rom

1) Flash Magisk v9

2) Flash phh's SuperUser r266-2

3) Reboot to OS

4) Install Magisk Manager v2.5
[Magisk] putridfoetus:
Install phh superuser app from play store.
[Magisk] stifuco:
does anybody have idea of how to do this?

Thank you
[Magisk] Nonononoki:
Hello,

I'm currently trying to get Magisk working on my Sony Xperia Z1 Compact. I'm currently on CyanogenMod 12.1 (because the article says that it won't work with Stock Sony Boot Images(?)). Does anyone know if it's possible?

Thanks in advance.
[Magisk] jcrompton:
Yes you have to install the phh superuser app and give root access to the Magisk Manager app. Then go to settings and check Magisk Hide

Then reboot

If it doesn't work reboot again and make sure Magisk Hide stayed checked

Also the kernel has effected me as well. A more stock kernel worked and another kernel didn't.

Remember if you flash another kernel or boot image you have to reflash Magisk v 9 and the Magisk superuser 266 module
[Magisk] bigcid10:
Is it pretty safe accurate statement to say that AP is working with the current combo

of magisk 9 ,MM 2.5,and the new phh 266-2

because I have SN and pokemon go working with my combo now (SU4,elementax,suhide,rootswitch)

but AP doesn't work

If it's not a safe bet on a HTC 10, there's no sense in blowing my phone down for nothing

I'd like to know , Thank you
[Magisk] teddy0209:
Both john(the dev) and the captain(his tester) uses htc10...
[Magisk] Artim_96:
When you are on CM you shouldn't have problems with Magisk. It's only a problem if you use the stock Sony ROM without a different kernel because Sony packs it's kernel in the .elf format which currently can't be manipulated yet
[Magisk] x_one:
On my Z3C i use AdvancedStockKernel and Magisk was working fine (when I tried it, but v8, didn't tried v9).

I couldn't manage to work systemless app adding so I gave up and I don't use it anymore. But maybe i should try again.
[Magisk] Didgeridoohan:
Have you tried the trick with starting to add a new card in AP, but then backing out, thus forcing a recheck of your root status?

Or just to add your card again?
[Magisk] rgshah3:
Does magisk v9 work with the stock firmware on moto x play? Or even the moto g 2015 as a matter of fact
[Magisk] DodoGTA:
Setup:

Device: Samsung Galaxy Trend Plus (GT-S7580)

ROM: CM 12.1 (Android 5.1.1 & LMY49J)

Addons: open_gapps-arm-5.1-nano-20161118 and latest version of Magisk, Magisk Manager and PHH Superuser

SELinux is in Permissive mode, both su files are removed and Magisk Hide is enabled (and I also rebooted after enabling Magisk Hide)

Some debug info:

magisk.log (Blame Tapatalk, not me for forcing me to upload it in .txt file extension): http://cloud.tapatalk.com/s/5831edae9e029/magisk.txt

More info will be added upon someone's request
[Magisk] Didgeridoohan:
I believe SN will fail with SELinux permissive, but I might be wrong... Don't really bother with SN.
[Magisk] Artim_96:
It's not that hard. You have to get the template, create a folder app or priv-app under system and put your apk there make changes to module.prop following the instructions there and in the readme.md, rezip that all and flash it through recovery (e.g. over the + button in the modules section of the manager) and done. That's how I installed WakeLock Detector systemlessly to /system
[Magisk] viroxnet:
Huawei p8 gra-l09:

*****************************
magisk v9 boot image patcher
*****************************
- mounting /system(ro), /cache, /data
- device platform: Arm64
chmod: /futility: No such file or directory
- constructing environment
- /data/magisk.img detected!
Mknod: /dev/block/loop0: File exists
- mounting /data/magisk.img to /magisk
- found boot image: /dev/block/mmcblk0p27
- unpacking boot image
15920 blocks
- restoring boot image with backup
/tmp/updater: Line 366: /dev/block/mmcblk0p27=/data/stock_boot.img: Not found
15920 blocks
- creating backups
49152+0 records in
49152+0 records out
25165824 bytes (24.0mb) copied, 0.345651 seconds, 69.4mb/s
- patching ramdisk
(android m policy compatibility mode)
libsepol.policydb_index_others: Security: 1 users, 2 roles, 795 types, 0 bools
libsepol.policydb_index_others: Security: 1 sens, 1024 cats
libsepol.policydb_index_others: Security: 87 classes, 8785 rules, 0 cond rules
- repacking boot image
! Boot partition space insufficient
! Remove ramdisk backups and try again
! Boot partition size still too small...
! Unable to install magisk
updater process ended with error: 1
i:legacy property environment disabled.
Error installing zip file '/external_sd/aplicaciones android/magiks root/1-magisk-v9.zip'
updating partition details...
I:data backup size is 5869mb, free: 2563mb.
I:unable to mount '/usb-otg'
i:actual block device: '', current file system: 'auto'
...done
i:set page: 'flash_done'
i:operation_end - status=1
i:set page: 'clear_vars'
i:set page: 'install'
i:set page: 'main'
i:set page: 'clear_vars'
i:set page: 'main2'
i:set page: 'advanced'
i:set page: 'confirm_action'
i:set page: 'action_page'
i:operation_start: 'copy log'
i:copying file /tmp/recovery.log to /external_sd/recovery.log
[Magisk] alexpower:
Ok
[Magisk] DrunphO:
same problem here :(
[Magisk] vampire_8_7:
SafetyNet and Android Pay fails now

Hi mate, I have just blown the combo you have which was working and tried Magisk + Phh's and the rest of it. I can say it doesn't work now SafetyNet fails as well as Android Pay. Save your time bro :D. I will revert back now to the working combo got AP working for almost 3 weeks straight :good: , am not sure why AP isn't working for ya because it's working for me fine on N9 running Paranoid Android, and N6 running PureNexus and both got Stock or the rom's Kernal.
[Magisk] The MAZZTer:
Magisk v9 does not work on Pixel C. The device will always boot to recovery as if I selected boot to recovery from the bootloader until I remove it.

v8 works fine.

If I upgrade to v9 with the Manager or flash the ZIP, either way it happens.
[Magisk] bigcid10:
no,but I will try and report back ,Thanks

but I don't have to do this everytime ?

I hope not,lol
[Magisk] williamlaw:
Just tried to test with XenMobile but still detected device was rooted.

Thanks
[Magisk] CM_boneZ:
You can find another updated uninstaller in the main thread.

---------- Post added at 07:55 AM ---------- Previous post was at 07:32 AM ----------

Magisk v9 seems not to work on Xposed v86.6 Systemless. I went crazy flashing there and back again with different zips but when I reverted back to Magisk v8, Xposed worked like a charm.

What I did was:

* From my current custom ROM, which CM 12.1, I booted to TWRP and wiped /system, /data, /cache, dalvik-cache.

* Flashed a flashable, deodexed, rooted stock ROM for my device.

* Rebooted the device.

* Full unroot using the built-in SuperSU.

* Reboot to TWRP again.

* Flashed SuperSU-2.78-SR4 systemless-ly (using "echo SYSTEMLESS=true > /data/.supersu")

* Rebooted the deviced and waited for the dalvik-cache to rebuild.

* Installed Magisk Manager v2.5.

* Installed Magisk v9 using Magisk Manager.

* Rebooted.

* Installed Xposed v86.6 Systemless by topjohnwu thru Magisk Manager.

* Rebooted (I noticed that that dalvik-cache did not rebuild.)

* Installed XposedInstaller by DVDandroid (the latest one).

And it said that the current Xposed framework is installed but not active.

* So I rebooted again. (Still no luck)

* I full unroot again using SuperSU.

* Rebooted to TWRP and flashed phh Superuser r266-2 (I thought that SuperSU and systemless Xposed doesn't work well together on 5.1.1).

* Installer phh Superuser app and when I go back to Xposed installer itis still not active.

* Tried reflashing Magisk v9, phh Superuser, and Xposed all at once.

* Xposed is still not active.

* At this point, I nearly got pissed but what I did was tried to revert to Magisk v8. When I rebooted, the dalvik-cache rebuilt itself!

* When I checked Xposed, it is now active.

* I uninstalled, phh, and go back to SuperSU systemless to see if Xposed will still work and it did.

So my verdict was the problem is in Magisk v9. I can't provide logcats or something because the laptop is with my gf now.
[Magisk] dagoban:
delete
[Magisk] Laico:
v9 bugs on meizu m2 mini

If on TWRP 3.0.2 I flash V9 on a clean Stock rom (flyme 4 android 5.1) boot crash and need flash a clean boot through fastboot

If I update to v9 through magisk v8 apk boot mod work well and system start up. hide su, root phhs 266 (sometimes I lost root with 266-2 ) and busybox works but xposed don't work same error than other user's installed but not active in xposed installer for systemles.

Sorry for my bad English and thx for magisk
[Magisk] DirkStorck:
Hi when I flash a new version of my kernel I normally do the following.

* Flash kernel

* SuperSU

* Magisk v8

normally than I have magisk with all my previously used modules.

But now when I do the same with the new update and I flash Magisk I see in the logfile that it creates a new magisk.img. So all modules are gone and xposed is gone too..

Any ideas what the reasons could be?

Thank you!
[Magisk] Genericxx:
Does Magisk V9 with Magisk Hide work flawlessly to hide root after november security patch on CM14.1 based roms? I am usually running SuperSU + suhide but the latter won't work anymore.
[Magisk] dimm0k:
is adding a module in Magisk Manager essentially the same as flashing the module in TWRP?
[Magisk] Artim_96:
Yes
[Magisk] duowing:
For a moment there I thought SN had been updated and wasn't passing, but it turns out I had just lost root and needed a reboot. I know this happens on the HTC 10, but it also happened on a One M9
[Magisk] dimm0k:
since zip files can't handle symbolic links, how would one create a module that create some links?

also, anyone able to flash the live boot module created a while back under v9?
[Magisk] harpin14789:
Why am I still not passing safety net?

Had supersu before no magisk. I did full unroot through supersu app, then deleted the supersu folder in recovery. Flashed kernel, then flash magisk v9, then phh superuser 266-2.

Enabled magisk hide.
[Magisk] twcobra:
I am using ABC and Flash kernel on my 6P. I found that flashing Flash kernel after magisk v9 and phh superuser 266-2 is what works for me. I would suggest:

Remove magisk v9

Flash boot image from your ROM

Flash magisk v9

Flash phh super user 266-2

Flash latest Flash kernel.
[Magisk] dimm0k:
how did you get that crazy looking battery?
[Magisk] twcobra:
3minit battery mod. I will usually make the mod and share for what ever ROM I am running at the moment. I have been on ABC ROM's for the past few months. I usually run either kantjer or ezio's builds with DUI
[Magisk] yochananmarqos:
Both Magisk & phh patch the kernel, so you need to flash the kernel first, not after.
[Magisk] hokiealumnus:
Just as further confirmation, I re-packed it with 7-zip and it worked fine on my G3 as well. No idea why the original doesn't work, but it's a simple fix, and now it's good to go until the next version. :good:
[Magisk] twcobra:
I am not sure why this is acting this but if I flash Flash kernel before it does not pass. I flash after then it passes. Maybe [MENTION=5196311]flash[/MENTION] has something special in his kernel.
[Magisk] Artim_96:
Was SuperSU systemless? If not, get the unsu-update.zip by osmosis, flash it and afterwards restore your stock system partition.

If it was, check if there is still the su.img in /data and delete it. And better start again by flashing your stock boot.img and then the rest. But try if you pass safetynet before fishing anything new. If you don't pass without Magisk and root, you won't pass with.

---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------

What exactly do you mean, what exactly do you want to do?

If you tell us, we can tell you how to create a module that does what you want. Maybe you're just thinking too complicated
[Magisk] harpin14789:
Supersu was systemless. I remember magisk installer saying that my ramdisk was still patched by supersu and that it was adding supersu patched would that have caused issues?

I will try and start over and see.
[Magisk] dimm0k:
I'm trying to create a module for 'mc', that gets installed using this http://nativnux.com/?p=43 installer. That installer installs the console midnight commander file manager into the /system directory and in /system/xbin it creates symlinks to mc... I was able to pull down the files it installed to various directories in /system and the only thing that remains to complete this module is to have the symlinks it creates. any suggestions?
[Magisk] Artim_96:
... What would happen if you wouldn't try to put it there via a symlink, but in your zip into /system/xbin? Wouldn't that just create a symlink there to the real files?

I mean I don't know exactly how the systems methods manage to let apps see the files as they where really there even if they aren't because of systemless, buy I'd guess the principle shouldn't be that different.
[Magisk] dimm0k:
hrmm, apparently I'm doing this in Windows... which doesn't handle symlinks at all, so I may have to try under Linux... is that what you meant?
[Magisk] Artim_96:
No. What my theory is, is that you might not need to create a symlink to the files but just place them to /system/xbin.

But that's just a theory, maybe someone knowing that stuff can say what's possible.
[Magisk] putridfoetus:
Windows does handle symbolic links, but differently than Linux. (Think Libraries in explorer) with Linux, the command ln -s file1 file2 creates a symlink. You'll need to find out what files in /system/xbin are getting symlinked for mc, obviously.
[Magisk] dimm0k:
so I just created a module for Midnight Commander, but after flashing it in TWRP I lost root... any ideas why this happened? attached is a copy of the module if anyone would be so kind to take a peek
[Magisk] jcrompton:
I've gotten many different roms to pass safety net on my N6 using Magisk v 9 and Magisk hide

Even CM 14.1 based roms like cdroid. But for some reason I can't get Nitrogen 7.1 to pass. Tbh I can't get it to pass unrooted.

I don't really understand all the reason that SN doesn't pass ..... Any ideas on what to try or why N6 Nitrogen ROM can't pass?
[Magisk] putridfoetus:
I don't know anything about midnight commander, but I can tell you the share and libexec directories in your system folder will not get added, since those don't already exist under device's /system. Share may be /system/usr/share? No clue about libexec..
[Magisk] jsaxon2:
Just a quick look, but you should remove the Replace example in your config.sh

This is an example REPLACE=" /system/app/Youtube /system/priv-app/SystemUI /system/priv-app/Settings /system/framework "
[Magisk] dimm0k:
hrmm, that will be good to note... but this alone shouldn't kill SuperSU would it? I mean even after flashing SuperSU again it's still not there so I'm currently removing Magisk, SuperSU and re-doing everything because something in this module I created broke it =(

the config.sh was stock, at least the bottom half was... you'll see the line after that REPLACE is another REPLACE="" to cancel out that previous line...
[Magisk] danielcr12:
is anyone able to boot the lasted cm13 nightly after installing xposed from the magisk app?
[Magisk] SamuelBegui:
That's due to the November security patch. As of now, if you're on the latest recent build you'll bootloop.
[Magisk] -Happy Feet-:
that's curious. I have installed Magisk and add some apps to the hide list. and what's happen? safetynet helper is red but Apps like Pokemon Go works... but I Uninstalled xposed before. maybe this is the reason.

anyone trying the magisk xposed module?
[Magisk] reas0n:
Hello guys, is it possible to run a binary as root using Magisk (for example by making a module for it), but without rooting the device itself?
[Magisk] Santiago2812:
Magisk V9 Update Error

Hi, well, i had magisk v8 installed, so i entered to magisk manager to update it but i got an error saying i had to do it manually, so i reboot my phone in twrp to flash the zip, and after that my phone went to a white screen saying there was an error:

Func 10 boot image

Error no2 load failed

So i download the update.app of B317 marshmallow ( i think that is the OS version i was using before) and extracted the boot img and recovery img and flashed both from fastboot. but now i get a bootloop and i cant make a backup of what i had on my phone and i dont want to make a factory reset

THANKS
[Magisk] viroxnet:
it's posibble to force install with that size?

- Repacking boot image
! Boot partition space insufficient
! Boot Size: 25165824
! New Boot Size: 25305088
! Remove ramdisk backups and try again
! Boot partition size still too small...
! Boot Size: [B][COLOR="SeaGreen"]25165824[/COLOR][/B]
! New Boot Size: [B][COLOR="Red"]25239552[/COLOR][/B]
! Unable to install Magisk
Updater process ended with ERROR: 1
[Magisk] Iceyogurt:
Tried to include some binary files in my mod, ended stuck at first screen, I mean the Android logo. But magisk.log told me everything was mounted successfully and my phone was done with late_start service mode. Weird.
[Magisk] viroxnet:
install in twrp or uncompress and flash with fastboot

https://www.androidfilehost.com/?fid=385035244224383592
[Magisk] formula91:
I am on Magisk V9 with Phh Superuser 266-2

When I enable Magisk Hide and reboot, I have root access for the first few seconds, and then I lose root and cannot use it in any of my apps.

I also sometimes get a notification saying my SU Binary needs to be updated. This only occurs when magisk hide is on.

I have tried reinstalling 266-2 over itself with no results. SELinux Enforcing or Permissive gives me the same results.

I have not checked any app to hide root.

I am on Nexus 5X Android 7.0 with the latest November Patches.

Can anyone help me resolve my issues?
[Magisk] Santiago2812:
Hey, thanks, i worked, but i when i turn on my phone i realized that everything i had on internal storage was erased. :(:(

Was that suposed to happen? Is there anyway to retrieve at least phographs and whatsapp chats
[Magisk] yochananmarqos:
Flash your stock boot.img or custom kernel, Magisk then the phh module.
[Magisk] formula91:
I tried flashing over everything and it didn't work. Should I try uninstalling magisk and and then try again?
[Magisk] alexpower:
It's not a bug it's a feature.

Problem known, reboot helps

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] ghbuur:
i could solve it with flashing uninstaller and flash magisk/phh again. since then no more loss of root with enabled magisk hide
[Magisk] yochananmarqos:
Whoops, forgot to mention that. Yes, flash the Magisk uninstaller first.
[Magisk] formula91:
Thanks I *think* I solved it. So far so good though. Here's what I did:

I uninstalled both Superuser and Magisk Manager apks.

Booted into recovery and flashed the uninstaller magisk zip

Booted into bootloader and flashed the stock boot.img using fastboot

Rebooted to system and let it settle for a minute or two.

Reboot into bootloader -- I had to reflash TWRP recovery since flashing the stock boot removes custom recovery.

Rebooted back into recovery and flashed my custom kernel (Elemental EX 3.10 for Nexus 5X, I did not choose anything different from stock other than a mild overclock in the AROMA options)

Flashed Magisk V9

Flash Superuser Module

Booted into System and Reinstall Magisk Manager and Superuser Beta 9 APK

Turned on Magisk Hide

Reboot

Turned on systemless hosts

Reboot

So far so good!

I suspect that the order of installation of components and what happens in between is what causes this error, so I just nuked as much as I thought was relevant and started over.

--Edit--

Suspicion was confirmed, a BetterBatteryStats Module that I used was constantly tripping Magisk Hide.

Removed the module, problem gone.
[Magisk] Skyrocket2Paradise:
Any issues with v9 and dp2? More specifically on the 6p?
[Magisk] Black_Eyes:
No i mean.

If i'm running stock at the moment and flash magisk on it, then afterwards i can flash custom rom without wiping anything? It will work?

---------- Post added at 05:40 PM ---------- Previous post was at 05:40 PM ----------

No i mean.

If i'm running stock at the moment and flash magisk on it, then afterwards i can flash custom rom without wiping anything? It will work?
[Magisk] kryptikal:
I'm having a similar issue.... removed all traces of supersu and systemless xposed, wiped system, cache & dalvik, flashed rom, gapps, elementalx, magisk, magisk compatible phh... after bootup I open the magisk app and try to toggle "Root Mount Toggle" off but it turns itself back on... will try to attach a video if I can.
[Magisk] N00dle:
I forgot to mention I'm running on a Nexus 5x and I used the Xposed 86.3 sdk23.
[Magisk] mobileman88:
The magisk app says that Android pay should work. However, safety net helper says response validation failed
[Magisk] topjohnwu:
Please take a look at the OP You need to have phh's superuser app installed.

My Magisk Manager is poorly programmed and it will crash if it detects root binary but cannot get root access.

It is just a POC. I'll release source code soon, also add more info the the first posts.
[Magisk] joeyddr:
Toggles don't seem to work it shows root access but when i toggle nothing happens.
[Magisk] azz06:
I'm using Samsung G920F. Installed and everthing works, except when I try to Toggle Mount Root back on after using SafetyNet it doesn't work. However a reboot brings root back.

Strange.
[Magisk] ShapeShifter499:
[MENTION=4470081]topjohnwu[/MENTION] The BusyBox you use for this is broken or maybe I'm using it wrong? It fails to fetch files files with wget, always a "bad address". I don't see this if I use the wget from Meefik's BusyBox. Any ideas?
[Magisk] bobby janow:
Similar question, but running Android N DP5 on a 5x. I don't believe Flashfire installs SuperSu 2.76 routinely, however. The only way I could flash the Magisk zip is to use Flashfire since I have only stock recovery and no access to twrp until that is fixed. Has anyone given it a try on dp5? I'm not interested in Xposed only AP.
[Magisk] ShapeShifter499:
[MENTION=4470081]topjohnwu[/MENTION] About the wget issue, are you compiling this version of BusyBox yourself? Seems the issue with "bad address" is down to which libc is compiled against. As suggested by the following three posts https://github.com/guardianproject/lildebi/issues/161#issuecomment-75177581 https://stackoverflow.com/a/26976653 and http://lists.busybox.net/pipermail/busybox/2011-April/075469.html You need to get it compiled against bionic (android alternative) instead of libc
[Magisk] kryptikal:
Captured a video of it toggling itself back on... Magisk Root Toggle Issue
[Magisk] Knaspast:
Would this allow me to log into snapchat without uninstalling xposed or disabling + rebooting in the case of systemless xposed?
[Magisk] Fentadroid:
Let me show you if i underestand everything.

I have a Oneplus 3, now with systemless root.

- I will flash the stock rom once again to remove SuperSU, formatting system partition

- I have to install Magisk-v1.zip

- Then phh-superuser-magisk.zip

- phh's SuperUser App

This way to have a working Android Pay.

Is that correct?
[Magisk] Chahk:
Nexus 6P running stock 6.0.1, previously rooted with systemless SuperSU 2.76, and 86.2 systemless Xposed. I wanted to have root, Xposed, and AndroidPay working. Here's what I've done:

1. Full unroot via SuperSU app. This also uninstalls the app itself and reboots.

2. Reboot to bootloader and restore to stock boot.img via fastboot.

3. Boot to TWRP and flash latest version of Magisk.

4. While still in TWRP flash phh's SuperUser (Magisk compatible.)

5. In TWRP flash 86.3 Xposed.

6. Reboot system, wait forever for the apps to optimize.

7. Install phh's SuperUser app from Play Store.

Everything is working well! Use Magisk Manager to toggle root off and AP works. Toggle root back on and enjoy all the root apps you've been using.

The only downside is that because I switched superuser apps, I now have to grant access to every root app all over again. If you have scheduled overnight jobs in Titanium Backup, those will fail unless you grant the request ahead of time.