yashsingh1/xdaforums huggingface dataset:
[Magisk] IzaacJ:
Sadly no. We didn't manage to get it to work.

I have previously been able to install Chainfire's SuperSU, but have not done anything like that since I got the tablet this summer.

Edit: I've opened an issue on GitHub: https://github.com/topjohnwu/Magisk/issues/24
[Magisk] culiacanazo:
Stupid me, if that's a custom rom there has to be either a recovery or bootstrap. If it's a (custom) recovery, bingo!

If it's a bootstrap... I feel your pain brotha!

Unless there's a stock one (if such coexistence is even possible), in which case i would guess/assume flashfire did mature to the point where you could use it as a bootstrapper.

I highly doubt it because even though i will not buy a bootloader-locked device, i think i would have heard about it by now.

What i do know for certain though, is that I'm trailing far from the path now.
[Magisk] culiacanazo:
I'm sorry, what method is that which you speak of?
[Magisk] meistr91:
Sorry from me:D whole installation of this magisk9, magisk manager, sudohide on xperia z5comapact 6.0.1 with superSU 2.78 installed and xposed 86. Thank u!
[Magisk] culiacanazo:
Ok, basically it all comes down to BACKING UP.

I really do wish i could provide the answer you're looking for, but i mostly play with Sammy. What i can do for you is, remind you, ALL operations of this type carry a risk, but if done properly, you can, if installation isn't successful, worst case scenario, restore your nandroid and you will have only lost a few minutes and not a device or a few dollars fixing it.

On a more "fear not" type of note, there's a magisk uninstall zip provided.

But do keep in mind how your flashes play with other installs (when it comes to boot image patching and whatnot...) Personally, i keep an original boot.img in my card, to save me any potential headaches, just in case!

Just between the two of us, i don't see why it wouldn't work
[Magisk] meistr91:
Back up is always important:p what im asking, im already rooted with chainfire superSU 2.78 do i need to uninstall it first before begining with a magisk steps? Cuz installation instruction is bit fuzzy for me:/
[Magisk] culiacanazo:
If you uninstall it you run the risk of losing root, i don't know, different ROMs have reacted differently in the past for me. Yes, you still have the recovery, but in some cases (i own a klte), i haven't been able to m make it work without reflashing the whole rom. That said, and since we want everything to run buttery smooth, i would switch to phh's (but then again, the last time i had a Sony in my hands, it was a Walkman lol), there's a sequence for flashing that varies depending on what you decide to go with, keep an eye out for it. Also any custom kernel? (It's a rhetorical question).

How you'd probably be safest going about that root, uninstalling prior, and all those inquiries you pertinently have, is to use a supersu removing zip and preferably do the rest in the same visit to the recovery ONLY if you'll be switch super user apps... (lately, you should forget the built in "uninstall" option, just to be safe, when doing surgeries like this.

If you decide to stick to superSU, make sure first that you're on SR5, and i would just flash it if upgrading, boot right back into android to make sure binaries update fine, then go back into recovery and handle the rest of the zips
[Magisk] oreo27:
What I did was install Magisk over it and it works like a charm. Given that SuperSU was installed systemless-ly to begin with.
[Magisk] rgawenda:
I've one problem with setprop method. I can't regain root access manually, so I need to wait until unroot time-out, and this doesn't allow me to create a quick toggle.
[Magisk] minieod:
app wont install in system installer. might have to be flashed in recovery

but having the same issue. wont install itself with the v3/phhv2 combo
[Magisk] DDz_1888:
I got an error during installing v3

"

.

.

-Repacking boot image

!Your boot partition size is too small... unable to flash

Updater process ended with ERROR : 1

.

.

"

Tried on Galaxy S5 G906K (Korean variant of G901F)

all stock with systemless root.
[Magisk] teddy0209:
Just remove traces of the old app...

I installed the app manually myself...
[Magisk] grep_i:
He knows that the zip must be flashed in recovery, that's why he said to extract the apk from within the zip file and install it with system installer as an alternative to flashing it through custom recovery.
[Magisk] minieod:
Well...maybe oneplus 3 has some issues there. It wont install. Even after removing it from data/app.

I get the "app not installed. X" dialogue

Hmm. Not sure youre grasping my post
[Magisk] teddy0209:
If you have a module that can disable signature verification, you can also use that.
[Magisk] minieod:
Thank you! Had no clue there was that ability / modules that would do that. Installed xinstaller and it worked .

Makes total sense, since flashing in recovery essentially does just that

Appreciate the help
[Magisk] teddy0209:
No problem...
[Magisk] Apexpredator12:
I have tried that before it still didn't work. Just tried it again there and still didn't work
[Magisk] grep_i:
OK sure I guess your right
[Magisk] CRXed:
You wait for a year to just try to flash a CLEAN STOCK ROM to start over? :confused:

You've been messing around on your phone for weeks, according to all the posts in every other Xposed thread...you are clearly doing something wrong.

Start over, stop messing with uninstallers and just flashing parts of your ROM...go all the way and start fresh.
[Magisk] Apexpredator12:
November I didn't wait a year I meant I tried it a year ago then gave up. And weeks? Commenting on posts and threads about pokemon go modules isn't messing around with xposed

I'm going to install a new rom still have the stock I got with my phone atmo. Just need to find out which one will work for me and not brick my phone with there being different models
[Magisk] topjohnwu:
Magisk v4 will come soon, this will be the super stable version that will work across most devices

It shall fix all boot image issues (non-standard boot image is another story)

In the extreme case, the Magisk will only add less then 12kb of stuff into ramdisk, it will definitely fit in any boot image.

And BTW, I'll also release a COOL stuff along with v4 :), you'll be happy!

Lastly, the recruit of Android Pay tester team will be soon, please stay tuned ;);)
[Magisk] ryandxter:
well well I'm here just to give specific classification / explanation about what is this projects do

I'm here to say that this method is about modifying boot partition to make systemless works (correct me if I'm wrong), since my device was Xperia Z3 then this require "unlocked bootloader" for any Xperia device in case to use custom boot.img script from this projects... please please OP underline this before another people from Xperia users with locked bootloader flash this projects, thanks

I'm already tried on myself almost hardbricking my phone and this isn't funny
[Magisk] Wilsse:
Thanks for the heads up. I have root with a locked bootloader (Xperia Z3 Compact) and would have attempted this.
[Magisk] chrisc93:
I can confirm that Android Pay is working. I have a Nexus 5X with a custom build of PureNexus running. I was able to use Android Pay w/Magisk at both Trader Joe's and Whole Foods yesterday afternoon.

Awesome work [MENTION=4470081]topjohnwu[/MENTION]!
[Magisk] sansnil:
Nice! Do you run Xposed at all?
[Magisk] chrisc93:
Nope, I'm not running xposed.
[Magisk] Vegasden:
Since the latest PN is not rooted, what root method did you utilize?
[Magisk] culiacanazo:
Mods, I'm trying to melt in, and try to keep it relevant. If i veer off to where it borders on what's good forum etiquette, please guide me, as that would help me identify it and mold accordingly. Thank you

---------- Post added at 01:16 PM ---------- Previous post was at 01:14 PM ----------

See? The world belongs to the go getters! Right on!

However I'm chuckling as i picture you flashing while i typed all that lol :P

---------- Post added at 01:16 PM ---------- Previous post was at 01:16 PM ----------

Oh s*it, major mix up, my bad
[Magisk] Kany3:
Thanks for the info and yeah it is a custom rom. When i use arter97 kernel everything work as far as magisk and suhide. But it break some of the rom feature . Like AOD flash light toggel and blue light filter.
[Magisk] meistr91:
Mine superSU was included in a rom, how I can know is it systemless or not? Sorry for dummy questions:/
[Magisk] oreo27:
No such things as dummy questions! See below:
[Magisk] meistr91:
[MENTION=4863028]oreo27[/MENTION]

Device xperia z5 compact xpower 5.0 rom (rom is based stock)

SuperSU 2.78

Xposed v86
[Magisk] oreo27:
Check if the directory I posted previously. They should be the same structure. If they are, then they are installed systemless-ly. I'm not 100% sure though since you're using a custom ROM.

You'll want to uninstall Xposed first and install it systemless-ly later if you're going through with installing Magisk.
[Magisk] HaloTechnology:
I am having probel installing Magisk on OP3 using the new beta 9 Android nougat , when i install Magisk 9 and phh it still shows no root and still wont pass safteynet
[Magisk] ammar18:
did you install phh superuser app?
[Magisk] HaloTechnology:
OK I was able to install with root but safteynet still trip even though I enables hide , it should work on nougat right ?
[Magisk] Toninho13:
I have bootloop after install V9 for a new system. The device is Vernee Apollo Lite. What can be the problem? Before this with V8 everything worked fine.
[Magisk] Didgeridoohan:
Did you reboot after enabling Magisk Hide?

Magisk Hide should take care of hiding Magisk, phh's superuser (Magisk version) and unlocked bootloader. Other things that may trigger Safety Net are Xposed, permissive SELinux and leftovers from previous/built-in root. Got any of those variables in your system?
[Magisk] meistr91:
This is what i found in /su/bin:

/su/bin/app_process

/su/bin/daemonsu

/su/bin/su

/su/bin/sukernel

And a lof of other files

But i cant find these:

/su/bin/supolicy_wrapped

/su/bin/sush

I found supolicy but not "supolicy_wrapped"
[Magisk] HaloTechnology:
I dont think so I flashed the stock room then MAgisk v9 then phh then enabled magisk hide then of course I restarted , any ideas ? do you think its related to nougat ?
[Magisk] Didgeridoohan:
Nope. Nougat should work just fine. How about providing a Magisk log?
[Magisk] HaloTechnology:
Here you go , thanks man I appercaite your help greatly :D

"** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide"
[Magisk] Didgeridoohan:
Hm... Do you have verbose logging activated? If not (which I suspect), please do (I'm not sure, but you might have to reboot after).

After "** Removing tampered read-only system props" it should show what prop was edited to hide an unlocked bootloader.
[Magisk] HaloTechnology:
OK I did that but here is the log :D

"** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide"
[Magisk] Didgeridoohan:
Ok... No change. So, I'm gonna make another assumption and say you did not reboot like I suggested. Or?

If I'm gonna have to make guesses like this it's gonna be hard to help... Help me help you dude. Details, details, details.
[Magisk] HaloTechnology:
No of course I did reboot here is the thing i think magisk hide is not working becuase I have an app root checker , what i do is hide root checker so i can check if magisk hide is working but its still grant it root even though its on the hide list :/

What do you think should reflash ROM and reinstall again ?

BTW it seems the uninstaller doesnt wipe everything I delete it the magisk folder in /data/ is there any place more then that ?
[Magisk] Didgeridoohan:
Ok, cool. There are bugs with Magisk Hide. I can't use it myself at the moment because of the "no root" bug where Magisk is unmounted after a while with it enabled (for that short period it works fine though). It's a known issue being worked on... For some it seems to be not so aggressive and a simple reboot fixes it, but on my Nexus 6 (Nougat, December patch) it kind of renders root completely unusable. Hoping for topjohnwu to find a solution.

Your log should show a bit more information after "** Starting Magisk Hide". Like you say, it seems to not be working on your device.

Don't know about the uninstaller (haven't used it).
[Magisk] HaloTechnology:
Thanks man you are awesome :) its such ashame that we cant have unlocked bootloader and we lose android pay :( why google why ?
[Magisk] Artim_96:
Doesn't manipulate Magisk v9 the kernel to hide that?
[Magisk] Didgeridoohan:
No, it uses the resetprop tool to hide it.
[Magisk] BananaYoghurt:
I'm using it on my LG G5 and everything works fine.
[Magisk] armando_rod:
If anyone is interested, I've pin down when the device loses ROOT to when you enable Android's Powr Saver mode, at least on CM14
[Magisk] KiranP23:
i am using magisk v9 and Magisk Manager , but i am unable to find Enable /Disable Root Toogle as shown in many online articles (Magisk Root is working but i want to temporary disable root )
[Magisk] kartikb:
There's no option to disable root. You can hide Magisk along with root from selected applications. You need to enable Magisk Hide, then from the list of apps, select the apps you want to hide root/Magisk from. Once done, restart your phone and it should all work. Make sure you have Phh superuser from topjohnwu for this, the Magisk version.
[Magisk] KiranP23:
Thank you , i have enabled and selected the application from list , but the selected app is not getting saved (after reopening app i am finding it unticked)
[Magisk] Didgeridoohan:
Yes it does, if Magisk Hide is functioning as it should. Which it didn't seem to do for HaloTechnology...
[Magisk] kartikb:
After selecting the app, restart your phone.
[Magisk] yochananmarqos:
I can't reproduce that on stock 7.1 1.
[Magisk] culiacanazo:
That's s rhetorical question.

I won't even assume.

I'm stating it.

And no, it's not the answer one would provide at your regular press conference

---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------

I haven't had that (or any, in my recent memory,) problem. If it helps

And by the way, i meant to quote [MENTION=4283035]armando_rod[/MENTION]
[Magisk] qounik:
could not normal boot. invalid kernel length

Samsung Galaxy j7-06 Exynos SM-J710F
[Magisk] Didgeridoohan:
Did everything flash without errors (recovery.log)? Have you tried a custom kernel? Also, have you checked the Samsung compatibility thread?
[Magisk] KyeWalker:
I'm probably walking straight into a face palm here but....

Why has xposed been ported to magisk modules when it trips safety net??
[Magisk] Captain_Throwback:
You're talking about two unrelated things.

Magisk is a systemless framework. Thus, Magisk is a means to install Xposed systemlessly. It has nothing to do with SafetyNet. Whether used systemlessly with Magisk or not, Xposed will trip SafetyNet. I fail to see how that relates to Magisk :confused:.
[Magisk] KyeWalker:
Haven't used magisk for a while since v7 I believe. I can't remember seeing anything let alone xposed being in the modules section in magisk. I knew the dev created systemless xposed, was using from the beginning of the pogo epidemic. Just didn't know if xposed in the modules section meant anything "special".

Maybe I should give these glasses a clean and read the description again lol
[Magisk] Odukle:
"this feature will not work without permission to write external storage"

This is the error I get every time I try to download magisk

I have a rooted device with super user free and have xposed modules, while not having a custom roms, I am using dirty flash to obtain oxygen updates for my one plus 3 phone

Please tell me what to do and if my super user is the one compatible with magisk
[Magisk] Artim_96:
Well, if DOWNLOADING is the problem it had nothing to do with Magisk. Use another browser or download it from PC and push it to your phone. Your browser clearly tries to download it to an external drive but strebt had permission for it.
[Magisk] Odukle:
Ic but it downloaded the manager and that is the file it is trying download it, what should I do to circumvent using the manager to download the file
[Magisk] darksaber79:
I need to trick some apps into thinking my mobile isn't rooted.

I was recommended to magisk.

I have flashed via twrp and then installed apk.

Appears to be working ok, can run the magisk manager.

But how do I set up to make an app think phone is not rooted?
[Magisk] Didgeridoohan:
Look for the Magisk Hide option in the Magisk Manager. Take a look in the Official announcement thread for info. There's a bug where root sometimes is lost completely. For most users it's enough with a reboot to bring root back. Should be fixed with the next version of Magisk.
[Magisk] AD2076:
[MENTION=4470081]topjohnwu[/MENTION] as you probably already noticed the latest Magisk (v9) doesn't install on Huawei devices (I own a P8) due to limited space in the boot partition, will you solve this issue? Is there anything I can do to help you?

Regards
[Magisk] chudy_85:
On my huawei mate7 I can install magisk v9 and I use all time
[Magisk] darksaber79:
Thanks Didger, I found the thread you mentioned.

I installed v8 as v9 would always show decompress error in twrp.

Will look at the end GA thread a bit more
[Magisk] putridfoetus:
What about setting read-only props? I understood before cache mods were deprecated that post-fs mode was the only way to set them. Is resetprop able to set read-only props in post-fs-data or service mode?

Also, would it be possible to simply symlink the binaries from the module directory to /system/bin? Is bind mounting really necessary?

I ask because I recall symlinking magisk's "busybox" binary to /system/xbin (or bin i don't remember which) because it wasn't there, and it worked pretty well.
[Magisk] CyberCROC:
Hi, hope you guys can help.

I did the following:

1. Installed the latest CM14 nightly for OnePlus 3

2. Uninstalled root

3. Installed Magisk (from TWRP)

4. Installed phh super user (from TWRP)

5. Wipe cache

6. REboot.

7. Installed magisk manager

When I try to launch the magisk manager it halts a couple of times.

Eventually I get it to start. All is showed as green.

When I go to settings and toggle "Hide Magisk" the check is cleared after some time. Even rebooting does not help.

I do not pass safenet verification so no Pokemon Go.

I'm sure I'm doing something wrong but read to most of the thread and can't seem to find.

Thanks in advance for any help
[Magisk] Didgeridoohan:
You don't mention anything about phh's superuser app... Do you have it installed? If so, are you sure your root is working?
[Magisk] CyberCROC:
I had not installed. Root didn't work.

Did the entire procedure again. Now all is working just fine. Thanks.
[Magisk] Artim_96:
Yes, Magisk hide seems to interfere with phh's SuperUser for some so will lose root when using Magisk hide
[Magisk] laggardkernel:
Setting read-only props works well with resetprop. It could set props from a file as well, very powerfull. More detail in the release thread. What i mean in your quote is that Magisk may take too much time at the post-fs-data stage during boot, and cause other apps which mount files in the post-fs-data stage as well failed to mount their files. Such as SuperSU and third-party kernels which mounting WiFi module in the post-fs-data stage. So i recommend reset props with service.sh.

I'm not sure whether mounting files to /bin MANUALLY will work or not. All i know is that don't try to mount binaries to /system/bin automatically with the "auto_mount" flag. I only use a trick to manually mount xbin binary now. I have not tested this method on /system/bin. Maybe [MENTION=6366997]UltraM8[/MENTION] has done this.

NOTE: You CANNOT symlink the binary files DIRECTLY to /system/bin, since symlinks will be generated in /system/bin. It will work but that's NOT SYSTEMLESS. And the busybox thing you mentioned is not symlink at all. It's just copy and mount. What we should do is to copy all the original bianries files in /system/bin to the "bin_bind" folder with correct permissions. Then copy/symlink your binaries to the "bin_bind" folder. Finally, mount the "bin_bind" folder back to replace the original /system/bin. I find this trick from phh's superuser, where it's used to mount su to /sbin. But i'm not sure if this will work with bin.
[Magisk] UltraM8:
No, not yet.
[Magisk] Henry1231:
Magisk working still?

Just wanna know if magisk v9 is still working for anyone. Bnot working on my s6 edge
[Magisk] Didgeridoohan:
And by "not working" you mean... what? Details, details, details, please...

All my modules are working just fine.
[Magisk] Henry1231:
I mean its not working for pogo, thats what i got it for. Android pay seems to be working.
[Magisk] Didgeridoohan:
So, what you're saying is that Magisk Hide isn't working as it should (not Magisk itself), at least for Pokemon Go? Is it working for other apps, as in can you hide root from, say, a root checker app? If it is working for other apps you should probably inquire in the Pokemon Magisk thread.

And just as a heads up, hiding root is not the main function of Magisk. So, just saying that it isn't working doesn't mean much... Always give some details when asking for help, it makes it a lot easier to help for those of us who can't read minds. :)
[Magisk] Henry1231:
Sorry about that. Magisk hide isnt hiding root from pogo. I tried root checker also but it didnt hide it either. Haven't been able to get magisk to hide root on my phone since v6. Any other suggestions?
[Magisk] Fild5x:
I am sure you mean using Magisk on your type of phone. I am currently using Magisk on my samsung galaxy a5h running on MM stock mod though only one modulei is working. That is viper4android. Trying other modules sends phone into seriuos bootloops. I have not tried xposed framework through magisk though am sure it can work. So i personally feel you can use it though you really need to know how toget out of any bad situation.
[Magisk] Didgeridoohan:
I can get Magisk Hide to hide root just fine on my system, but there are some prerequisites needed. Safety Net, for example, may get triggered by Magisk, root, Xposed, an unlocked bootloader and permissive SELinux (Magisk, root and bootloader state is hidden by Magisk Hide). Also, no previous root may remain on the system. The only problem I have with Magisk Hide is the "loosing root" bug where aggressive unmounting disables root, which for me makes it unusable at the moment. Should be taken care of with the next version of Magisk.

The next step, which honestly should have been among the first, is to provide some information and logs. So far you've only mentioned using Magisk v9 on a S6 Edge. You could at least tell us what Android version and ROM you're running, which root method you're using (at the moment Magisk Hide requires Magisk phh's superuser r266-2) and provide a Magisk log.
[Magisk] Wetzel402:
I have done a fair amount of research and believe the engineering boot.img we are using on Verizon S7s still prevents booting if the ramdisk is modified so SuperSU can't work in systemless mode nor can Magisk work. We are limited to system (not systemless) mods due to ramdisk modification requirements. We will only be able to use such mods if the Verizon edition S7 receives a bootloader unlock method...