yashsingh1/xdaforums huggingface dataset:
[Magisk] culiacanazo:
For starters, you should upgrade your super user to 17... Just saying
[Magisk] Fun_GKC:
The Magisk Manager keeps crashing, any idea?
[Magisk] culiacanazo:
Without logs, I'd have to be some sort of fortune teller, in which case i wouldn't even be here ;)
[Magisk] jhedfors:
When this happened to me, it was because I had not installed the superuser app. Without more information (logs), it is hard to tell if this is your issue.
[Magisk] Fun_GKC:
No matter it's rooted or not, the manager crashes anyway

http://pastebin.com/ZCxvc55y
[Magisk] culiacanazo:
One thing is being rooted and another one installing and opening phh's...

check?
[Magisk] culiacanazo:
So, how did it all end up? I just redid everything to try to reenact what the problem could be:

Flashed a nightly without wiping data, only(previously!!) wiping system and cache,

Used "su cleaning zips", the deep buffer remover, and uninstallers for both Magisk and my kernel

Flashed a "stock" boot image afterwards, immediately rebooting right back into recovery just to make sure what needs to settle, if anything, settles

Checked "mount system RO"(just trying to be thorough, although i realize it might sound contradicting due to the following reason) , flashed: Rom, Magisk, phh, (in my case it detected system install, so, after lastly installing my kernel, which is optional for you, i rebooted again into recovery)... reflashed Magisk and phh, this time going thru as systemless, then flashed my mods, when there are some (this case obviously yes), namely dolby, etc.

Rebooted, selinux permissive (unbeknownst to me whether that would be kernel-dependant). Double-checked my previously installed apps (viper, Magisk, and phh's, as they are user apps)..

--No stericson or supersu anywhere--

Went into Magisk and ticked busybox (along with the rest of my preferences), downloaded and flashed the latest v4a module from the manager, rebooted, opened v4a up, installed driver, rebooted, bingo!

Questions?
[Magisk] culiacanazo:
Negative.

7.1.1 here.

10.2

Latest v4a module

Everything's A-OK! ;)
[Magisk] Baconator724:
I know, but after it close the app it re- enables it, so after a restart it is still enabled.

And then SafetyNet not working is an issue too, as I have Magisk Hide on, use the latests version and have both root and Xposed systemless.
[Magisk] culiacanazo:
Perhaps it has to do with the browser's anti pop-up technology and/or adaway, but i can't see the log...

By clean install do you mean you wiped system? (it would be a good idea IF you had a system SuperSU)...

By restore i meant the boot.img but since you come from stock kernel I'd only need to know whether you had been systemless.

Sorry if I'm late and you've already put this behind you (it would be difficult to read backwards to see what has been taken care of and make a note of everything to back-connect it; hope you understand)...

And if anything (i haven't encountered that particular problem just yet), I'm pretty sure that even if Magisk detects it, it will override it once you flash phh's, in the right sequence, of course.

---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------

Let me know how that plays out, the minute i set to permissive i lose my sim card network/signal and access to settings becomes tricky

---------- Post added at 10:29 AM ---------- Previous post was at 10:25 AM ----------

May you be so kind to share with us the reason as to your immeasurable joy pertaining to the aforementioned elite club?

---------- Post added at 10:33 AM ---------- Previous post was at 10:29 AM ----------

Three posts above yours
[Magisk] mucha.k1994:
Well... When I install a v4a drivers from app (but question is WHY you do this when magisk module install drivers etc as module anyway?) I see after a while freeze - I/O problem. Drivers not installed. I have msgbox like your, I mean 2.5.0.4, Yes, Yes etc. But in processing I have NO.

And PS - if you don't switch your kernel to permisive before you install drivers from app - it shouldnt work, yes? So switch is a must? Ask because I never do that before installing drivers and maybe it is my problem? Anyway its just a question because I back my phone to 6.0 MM rom.
[Magisk] culiacanazo:
- My phone is in permissive because of many things that require it, thus it leaves me in the dark as to whether it happens to be a must for you or that's just how it works for me.

- You do realize that for it to say "processing" music must be playing, right?

- I've never had it come with the drivers installed if from Magisk
[Magisk] mucha.k1994:
Oh, okay then. I never know it before a lot of things can require a kernel change;

Damn, forgot to say - ofc, I play music when check this. Still NO;

Just unzip module and there are libs and .conf files for v4a. This is why when you fresh install module and app then you don't see any msg to install drivers etc. when first run.

First I think it's a module problem, maybe outdated libs or .conf files because I see on xda other files in flashable zips which work very well on nougat (from post, not my test) and I try also mod this module but unsuccessful.
[Magisk] alanmv567:
Which note 4 do you have and are you running Lollipop or marshmallow stock?
[Magisk] Artim_96:
SM-N910F with stock M
[Magisk] Chahk:
My ground is ready for some breaking!
[Magisk] dimm0k:
awesome! thanks for this bit of info and [MENTION=4470081]topjohnwu[/MENTION] for Magisk!

EDIT: speaking of boot animations, any way to get LiveBoot working with this?
[Magisk] Captain_Throwback:
Yes and no.

I'm using LiveBoot now, after having installed the app, and the LiveBoot script manually. But you can't use the app because it doesn't know to look for or place the LiveBoot script in the Magisk folder. So it'll work, but only with the default settings.
[Magisk] dimm0k:
where can I find the script and which Magisk directory should it be placed in? I'm guessing the default settings would be it would scroll over the ugly bright white T-Mobile boot "animation"?
[Magisk] Captain_Throwback:
That's the problem - you can't "find" the script, since it only gets created once LiveBoot is installed and given root access. If you're able to install the app and grant it root (even if the app gives you an error message and closes afterwards), you'll have to create it manually. The script produced by the app is called "0000liveboot" and contains these contents:

#!/system/bin/sh
/system/bin/sh /data/user/0/eu.chainfire.liveboot/files/liveboot &

Place it in the "post-fs-data.d" folder under /magisk with 750 permissions. The default settings simply replace your boot animation with LiveBoot - you shouldn't see your old boot animation at all. It's currently working fine for me.
[Magisk] dimm0k:
hrmm, I've done as mentioned, but upon rebooting I still see the ugly white T-Mobile boot screen. I have LiveBoot installed and was working prior to Magisk/phh superuser, created the script you mentioned and chmod it to 750 under /magisk/post-fs-data.d. anything else I might be missing? LiveBoot does have root access according to phh superuser.
[Magisk] Droidphilev:
Hi,

[MENTION=1162986]Captain_Throwback[/MENTION], i guess you are the perfect person to ask ;)

Is it possible that flashing Magisk to a secondary rom (stock) breaks something on a primary rom? I tried this on my shamu and it works fine but since then primary rom sometimes hangs and reboots. Not sure if these things can be related tbh.

EDIT: forgot to mention it's about MultiRom
[Magisk] Captain_Throwback:
No way I have any idea without at the very least a recovery log.

But it shouldn't have any effect on primary if you're flashing to secondary. It may be that multirom-edify needs an update to handle how Magisk patches the boot.img but that's really more [MENTION=2605798]nkk71[/MENTION]'s domain.
[Magisk] Droidphilev:
Thank you for the info! Next time i play with it i will get the log.
[Magisk] dimm0k:
[MENTION=1162986]Captain_Throwback[/MENTION] any suggestions?
[Magisk] Captain_Throwback:
No.

Wait for v4 and see if it makes any difference, I guess. It worked for me on v3 though.
[Magisk] Captain_Throwback:
One thing you can try is tricking LiveBoot into thinking your device has init.d support. I think it needs to initialize some files on first start, so that may be why it's not working for you, as the app has never opened successfully.

You can accomplish this by creating an init.d folder in /magisk/mounts/system/etc and then placing a dummy file there, so that the folder gets created by Magisk. You'll also have to create a zero byte file called "update" under /magisk/mounts/lists (or whatever it's called) so that Magisk creates the new folder on boot.

After you reboot, you should be able to open the LiveBoot app. If that works, LiveBoot *should* function on subsequent boots using the script you previously created.
[Magisk] JudgeDread11:
Hi everyone, if I uninstall magisk, to then reinstall. If I delete the magisk image file without resorting the stock boot image and reinstall, will this overwrite the backed up stock boot image with the modified image, out are there checks in place to actually verify the backed up image is not a poached image.

O will make backups of the original stock backup image, but I am just curious.
[Magisk] dimm0k:
grr, getting closer. after implementing what you listed here the LiveBoot app is able to open and install the script with no problems. the test run works as well, however when I reboot nothing happens! still the same white screen...
[Magisk] Captain_Throwback:
You still have the script from earlier there, the one in post-fs-data.d?

What's weird is that the test doesn't work for me, so that's interesting.
[Magisk] Artim_96:
Interesting question. For all I know there is no check of the boot image. However I think to render that at least the installer of the earlier systemless XPosed (86.0-86.2) or systemless SuperSU checked if there was a backup of that image and if so it would restore it and that patch it. I think the Magisk installer should behave the same, maybe someone can confirm that.
[Magisk] JudgeDread11:
When I reinstall I'll see what comes up in the logs. I'll post it here. :)
[Magisk] dimm0k:
yep, the script from post-fs-data.d is still there and I can also see etc still has the init.d directory and the liveboot script in there as well. perhaps Magisk v4 will aid in this...
[Magisk] culiacanazo:
- Why would you unzip it?

- It shouldn't be outdated if you get it straight from the Magisk manager app...

- While there are some versions out there that work enforcing, I'm inclined to believe that the one you're using needs permissive... Just check really quick, got nothing to lose
[Magisk] alego500:
Ohh probably. Fits in regard to the icon anyways.
[Magisk] mucha.k1994:
Just for sure and my curiosity.

Sure, but in marshmallow where I'm now this module work without change anything and I search solution for get the same on nougat (OOS from OnePlus 3).
[Magisk] culiacanazo:
A lot of things changed between one and the other.

Now we can sit here all day exchanging chit chat and annoy the crap out of mods for being off-topic borderline, or we can just try different things...

Remember, if you want the result to be different, gotta do things differently...

Do the same, you get the same results

Added: peeping in your zips is fine as long as you don't install them manually (nothing wrong with that either, if it weren't for the fact that we're trying to pinpoint a problem) :D
[Magisk] culiacanazo:
Probably...

Reading is a useful habit :P

It'll take you farther than a couple liters of fuel in a Prius, here in XDA at least ;)
[Magisk] Fun_GKC:
Sorry, I don't quite get what you mean.
[Magisk] culiacanazo:
Did you install this?

Some ppl seem to think that only flashing the zip suffices
[Magisk] Fun_GKC:
Yes, I installed. It asked for root permission but it still crashed.
[Magisk] culiacanazo:
If everything's followed to the dot, maybe it's time to open up a bug report, since it's not in the known issues

I would start all over just to be sure, and most likely your issue will be resolved, and it really doesn't take that long
[Magisk] Alpine-:
Same. Guys is you have this latest topjohnwu phh su installed and showing in magisk manager app, Install the phh superuser manager app (play store). That cured crash issues with Magisk manager. It was telling me I had root but nothing else detected it. The magisk manager app was crashing. Other apps had no root and I was seeing problems. 10.2 install /reboot process switched me from chainfire's su to phh modified topjohnwu r2. I'd never used anything but original chainfire's cf auto root and superuser. You need to install the phh manager app and enable superuser. It's working fine now. I just removed chainfire's superuser app since you need this phh modified topjohnwu root to work with Magisk Hide anyway.

Only remaining issue is cts profile mismatch error (safteynet fails) but this is a known issue with Samsung devices and their Namespace modifications. Hopefully a work around for that comes.
[Magisk] Link_of_Hyrule:
I'm pretty sure it's not possible but I'll ask anyways. Can Magisk replace the sounds inside of an app with other sounds? These aren't stored externally but are actually part of the app itself but if you unzip the app you can access them.
[Magisk] culiacanazo:
It sure sounds like something someone sometime would somehow wanna build! :D
[Magisk] Link_of_Hyrule:
The reason I ask is the message sounds in Allo don't play properly in Lineage OS 14.1 because they are a codec it doesn't like.
[Magisk] culiacanazo:
I don't even get the red "X", just a "refreshing", never-ending circle
[Magisk] Link_of_Hyrule:
Are you on Wi-Fi? If so try mobile data. Close and reopen the app.
[Magisk] culiacanazo:
Sadly, it didn't work. But does that have anything to do with it? Also, i don't really need it right now but you never know down the road... I've been disconnected from that type of development since i moved to Mexico... So allow me to ask, anything custom rom/kernel combo have to do with it? (Search me!)

Or maybe the fact I'm using microG? (Without xposed, i shall add)... Since those two screenies make up my whole log and everything else seems to pretty much be up and running.

Thank you
[Magisk] Link_of_Hyrule:
If you're not using the gapps I works assume you don't have SafetyNet and it will never finish.
[Magisk] rignfool:
Captain_throwback says you had a play services crash...

Reboom...
[Magisk] culiacanazo:
I kinda thought so, i guess I'll have to wait for xposed for mG's sig spoof'n.... It's Google-less or nothing for me lol

Thanks to both of you i can lay that to rest

Update, i couldn't actually hit thanks as it says i reached my daily limit :D
[Magisk] qu4gmire:
Does anyone know how the systemless Viper4Android compares to a regular installation V4A as a system app? Guides for 100% compatability that I've seen mention things like driver updates, etc. which I assume are taken care of by Magisk Manager flashing the zip... but only a few apps seem to run their audio through it. I'm skeptical about moving the apk to system/priv-app or something if the entire point here is to avoid modifying /system :confused:

Oh, the FX "compatible" setting doesn't seem to solve the problem either. I haven't changed my SELinux to permissive (option available within v4a's settings) while troubleshooting, though. I'm hoping to avoid that.

I have the same setup, and I'm almost positive SafetyNet can't work with microG. I get a CTS profile mismatch every time (but I can live without Pokemon Go).
[Magisk] culiacanazo:
Cool, let's be in touch once we can activate "fake gapps"

Also, i couldn't tell you that much, wish i could, but i do know v4a thru Magisk lacks nothing compared to traditional v4a, at least from what i can tell

And either way, it's the way it's going! Nothing to be done about it
[Magisk] qu4gmire:
I've already got all the functionality I need thanks to microG, but I'm happy to help you test stuff if our setup is especially unique. If [MENTION=3999488]MaR-V-iN[/MENTION] decides to add SafetyNet support, that's cool, but he's probably right to make it a low priority.

What do you mean by "the way it's going?"
[Magisk] culiacanazo:
Systemlessly, the way of the future

ADDit: And yes, even though I'm in Mexico, i have a big u.s. presence (my phone's American, albeit with a Mexican carrier, I'm a dual citizen myself, i use Pandora here, i keep a Google voice account, etc)... So yes, that's something i see myself as using in the not so distant future (the whole "fool-Google" thing) ;)
[Magisk] qu4gmire:
I'm very okay with that, but it's hard to tell what existing info about V4A (in this example) still applies to the systemless implementation. It's an unofficial, modified release, so the original creators won't be able to support it. And any guides available don't take the systemless method into account, so I don't know how to approach things that suggest I modify system for the sake of 100% V4A compatibility.
[Magisk] culiacanazo:
Gotcha! Perhaps the viper thread? I realize this time it involves Magisk, but to be honest with you, i haven't seen much here regarding output quality and comparing it, only as much as installation/compatibility is concerned
[Magisk] Jenanga:
I'm using magisk manager 3.0 and magisk 10.2 since v9 don't work the dark theme only white background
[Magisk] xXCoolGuYXx:
Hello I try your magisk on my lg v10 h901 20j 6.0 mm and it just put me in to fast boot when I try to boot, could anyone help me please?

An after I try to install it with the app the safeynet was still in red .
[Magisk] culiacanazo:
The easiest and only solution i can provide is uninstall, reboot recovery, wipe caches, and reinstall (there's nothing wrong with Magisk theme-wise)
[Magisk] afcaajax:
I still can't pass SN. Magiskhide is working since the latest version, but I don't know what I'm doing wrong

Verstuurd vanaf mijn SM-G930F met Tapatalk
[Magisk] lenard. furr:
Help with ResetProp

Hi all, I finally got Magisk v10.2 up and running and hidden and the last thing I need to do is to enable tethering. I understand that I need to use resetprop somehow, but I am not sure I fully understand HOW to do that. Any instructions I have been able to find thus far are super vague. Even the description of it on the official thread doesn't really do a good job of saying how to implement it. Is there any sort of step by step guide on how to use resetprop?
[Magisk] yochananmarqos:
Magisk does not hide Xposed, that's why you're not passing SafetyNet.
[Magisk] Baconator724:
It's systemless Xposed.
[Magisk] dreinulldrei:
Might still be it's not hidden properly. Also noticed that while I was passing Safety net the last couple of weeks, it's now a profile mismatch.
[Magisk] yochananmarqos:
Systemless Xposed allows you to install OTA's, not pass SafetyNet.
[Magisk] culiacanazo:
Google? I mean, you're in the Magisk thread
[Magisk] lenard. furr:
I've been googling for the better part of the past two days and my statement still stands. Anything I find is somewhat vague. I was posting in the Magisk General Support / Discussion thread because resetprop is a part of Magisk and I assumed the general support thread would be a good place to come for general support. Guess I will start a resetprop General support thread to get some more specific help.
[Magisk] culiacanazo:
I thought a read tether, i need glasses
[Magisk] lenard. furr:
No worries, you did read tether, but I was asking how to use resetprop so I could enable it.
[Magisk] culiacanazo:
Mea culpa, don't know
[Magisk] lenard. furr:
I was not able to find an end to end description of how to create a resetprop module, but I was able to create one using the shell of someone else's.
[Magisk] Captain_Throwback:
Create a module. Add a resetprop line to set whatever property enables tethering to post-fs-data.sh (and make sure you enable POSTFSDATA in config.sh). Flash module in Magisk Manager. Done.

The syntax for adding a resetprop line is in the official thread, and there's a thread for building a module (and the module template has a README). That should be everything you need.
[Magisk] Baconator724:
Oh, so it's impossible to have both Xposed and a positive SafetyNet result?
[Magisk] mucha.k1994:
Yes, It's true. Or just maybe "not yet"...? ;)

anyway, again: MAGISK + XPOSED = NO SN.
[Magisk] culiacanazo:
[MENTION=7963555]mucha.k1994[/MENTION] i realize you PM'ed me, but i there's no way to attach anything, and you know what they say, a picture is worth a thousand words... I mean, what else can i say? I don't know them to be included except in guitardedhero's prepackaged ones...
[Magisk] mucha.k1994:
Thanks for nice reply. But as I see, you don't have app from module, right? I mean it isn't 2.5.0.5? So, I think you just install module, then app from Internet and this is your build?
[Magisk] culiacanazo:
When i installed it, it was the apk inside the v4a dark zip found in the Magisk module thread, i don't link cause I'm not using the browser and I'm not aware how... Then, the update eventually came via the Magisk manager (remember i mentioned how after wiping and flashing a nightly my apps should still be there, since they were in /data?)
[Magisk] xXCoolGuYXx:
Hello could someone help me I have been trying all day to try and get magisk to work on my lg v10 h901 20j 6.0 mm on t mobile but I keep getting this even if I install it or not and if I flash the zip it just bootloops and the thinking I keep getting is the safety net thing could anyone here help me ?
[Magisk] qu4gmire:
For the record, the prompt you received asking to install drivers does not (or didn't for me) come up when you install by flashing through Magisk Manager and then installing the .apk that [MENTION=4470081]topjohnwu[/MENTION] provides in the support link (also in the Manager). At least one driver, the one it seems to be using, is active and available.

That's one example of how the installations differ between Magisk and official... dunno if the info might be helpful to anyone but there ya go!
[Magisk] culiacanazo:
Everything was already working, i i flashed a nightly, kinda like when you have to simply redownload hosts and stericsons, but the apk was already there, and the rest of the story is history.... From last night on... But we're both glad someone more knowledgeable can share his knowledge because like i said, what can i say?

ADDit: my apk didn't come from the one that topjohnwu provides in the support link, it was in the v4a dark zip found in the repo thread
[Magisk] Didgeridoohan:
Provide a recovery log from flashing the zip. Only way anyone can even guess what's going on...

Safety Net is Google's api for apps to verify your device is secure (not rooted among other things). It's got nothing to do with your problem.

Edit: Wait a minute... Doesn't LG devices need to "bump" the kernel? Maybe try looking that up. (I know nothing about it since I don't use LG)
[Magisk] qu4gmire:
Hopefully our exchange helps those more knowledgeable folks :)
[Magisk] xXCoolGuYXx:
Lg bump ? An how would I get the recovery log ? Where would I find that and would it still be there after I flash my back up because becusethats the only way I get my lg to boot back up .

Btw thanks for the help tho .

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

Okay flashed it again a few minutes ago and it worked weird ! Try to post the log but XDA won't let me post it, if you have a telegram for this mod it would be so great full and I can share it with you but thanks a lot tho .
[Magisk] piats:
Hello! I'm using OP3.

My data partition is formatted to f2fs.

Magisk works perfectly fine if I use Oxygen OS (stock) based ROMs.

However if I use CM or AOSP (custom) based ROMs magisk gets properly installed but there's no root.

If I use ext4 filesystem format magisk works fine with all ROMs.

However phh's SuperUser works fine without magisk with f2fs. I'm using phh's su version r275.zip for root.

I hope someone with more knowledge could look into this issue.

I can try to provide logs if needed.

Cheers!
[Magisk] Alucard:
Hello to the forum,i just installed the app and the super user phh,but dont know how to install the safety net,also does magisk work with supersu?