I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Wonder Wicked Witch said:
I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Click to expand...
Click to collapse
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
razr96 said:
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
Click to expand...
Click to collapse
Right Now I'm using Resurrection remix 5.8.5 kernal 3.18.31 twrp 3.1.1.1
It works in any custom rom, it is mostly useful for lineage os and los based rom because in los you cannot root easily, Magisk with ext4 filesystem is required. I'm not sure with the modules, super user works, safety net pass failed. If you just want root access you can give a try....
It works fine when you have a different kernel. A dev. on here reported that the only reason it doesn't work is because of how Lenovo implemented F2FS in the kernel.
No problem, everything works fine except that Safety net won't pass.
Related
I flashed the purenexus rom with elemental X kernel and a modified version of magisk 11.6 that was made for roms on the pixel. I was wondering if there was an update to this so I can upgrade to 12.0
I flashed v12 which I downloaded from this post
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845/post72045390#post72045390
Everything's working just fine (May PN + Elemental 1.11).
yeah me too. works great, very good combo
Here's the direct link to Magisk-v12.0-Pixel.zip: https://drive.google.com/file/d/0B1xZ4VKT4JKZUFhVUlk0enhBVFk/view
JimSmith94 said:
Here's the direct link to Magisk-v12.0-Pixel.zip: https://drive.google.com/file/d/0B1xZ4VKT4JKZUFhVUlk0enhBVFk/view
Click to expand...
Click to collapse
Has anyone been able to install this successfully? 11.6 works great, 12.0 after multiple attempts results in no root.
IlyaKol said:
Has anyone been able to install this successfully? 11.6 works great, 12.0 after multiple attempts results in no root.
Click to expand...
Click to collapse
I'm not sure it works, I'm getting a message saying functionality greatly limited
Bogega said:
I flashed v12 which I downloaded from this post
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845/post72045390#post72045390
Everything's working just fine (May PN + Elemental 1.11).
Click to expand...
Click to collapse
This didn't work for me for some reason, getting this https://imgur.com/a/rN4zi
tryfont said:
This didn't work for me for some reason, getting this https://imgur.com/a/rN4zi
Click to expand...
Click to collapse
Try going to apk mirror and installing the latest magisk manager. Also make sure NOT to enable BusyBox in it.
pcriz said:
Try going to apk mirror and installing the latest magisk manager. Also make sure NOT to enable BusyBox in it.
Click to expand...
Click to collapse
I had the latest (4.3.3) and still no dice. Magisk-12.0-Pixel doesn't work on my Pixel.
11.6 + Magisk Manager 4.3.3 works beautifully.
IlyaKol said:
I had the latest (4.3.3) and still no dice. Magisk-12.0-Pixel doesn't work on my Pixel.
11.6 + Magisk Manager 4.3.3 works beautifully.
Click to expand...
Click to collapse
I didn't quote you because your issue sounds like you need to wipe out the 11.6 folders and and reinstall 12. It's a different issue. I don't have a link but c_goodwin details how to do it in the RR thread.
do you have to run purenexus or can it run on stock?
pcriz said:
I didn't quote you because your issue sounds like you need to wipe out the 11.6 folders and and reinstall 12. It's a different issue. I don't have a link but c_goodwin details how to do it in the RR thread.
Click to expand...
Click to collapse
Fair enough; that was it. I ran the uninstaller as part of my May OTA/April BL flash and it updated to 12.0 successfully and am rooted. Thanks!
I'm running the May update of PureNexus with Magisk 12.0. Have root via MagisSU with root hide and busy box enabled and all is working well. Even pass safety net check.
how
mostyle said:
I'm running the May update of PureNexus with Magisk 12.0. Have root via MagisSU with root hide and busy box enabled and all is working well. Even pass safety net check.
Click to expand...
Click to collapse
I cant get 12.0 to work on my Pixel XL but i have 11.6+4.33 manager installed and works great. i tried many times to get 12.0 to work i even did a full restore to factory and then flased my Custom ROM (Pure Nexus) and then did the full install of 12.0 following the directions and still says no root limited access. but gone back to 11.6+4.33 no problems at all
how did you do the install of 12.0 and the 4.33 manager if you could give the steps please.
First of all i think there is a need in common thread about Magisk.
I am on XT1685 with 137-35 ver. and exprerienced some Magisk issues. MagiskSU works well on 12.0, 13 beta and 13.3. But SafetyNet is not. My particular problem is not mountable magisk.img. And there is a suggestion that may be caused by f2fs issue on some Lenovo devices (or something else). In different threads there are a lot of different messages about working/not working SafetyNet so i think we need clarification. Most people don't even bother to point out OS version, stock, custom kernel, model etc. So let try to gather information about issue together.
SafetyNet status: not pass
Model: XT1685
OS: Stock 137-35
Kernel: Stock
Magisk: 13.3
Have you also tried the universal safetynet fix and it still doesn't pass?
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Dahenjo said:
Have you also tried the universal safetynet fix and it still doesn't pass?
Click to expand...
Click to collapse
Magisk modules don't work with stock kernel
For OP, you should try a custom kernel, probably this will fix your safety issue
atrac17 said:
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
CaptPetrenko said:
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
Click to expand...
Click to collapse
V5 is for -67. That's why you had trouble.
atrac17 said:
V5 is for -67. That's why you had trouble.
Click to expand...
Click to collapse
Yeap.
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
manjot7798 said:
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
Click to expand...
Click to collapse
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
CaptPetrenko said:
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
Click to expand...
Click to collapse
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
manjot7798 said:
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
Click to expand...
Click to collapse
Can not say something about that. I never mounted folders. Use only Root Explorer for file managing. Do you have problems with SafetyNet? Could you send Magisk log? May be your mounting problem has common roots with stock kernel issue and read-only preferences
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
After updating to v. 14.0 ctsProfile error occured. I rolled back to 13.3 version but there was the same error. I flashed the latetst beta of universal fix and ctsProfile check went through. Don't know would it work with 14.0 ver.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Click to expand...
Click to collapse
CaptPetrenko said:
After updating to v. 14.0 ctsProfile error occured.
Click to expand...
Click to collapse
Hi,
Most of the work regarding the cts check can be done with a custom kernel.
And one relevant factor is remove the parameters "androidboot.verifiedbootstate" and "androidboot.veritymode" from the command-line (patching the "/proc/cmdline" file).
See this post: http://forum.xda-developers.com/showpost.php?p=73712158&postcount=471
If you like to pass the SafetyNet, then first use a patched kernel or request to developers to include this patch!
Don't waste your time with other complex solutions!
Hi,
If you like to pass SafetyNet in stock and have full support for Magisk then install this kernel:
https://forum.xda-developers.com/showpost.php?p=73783900&postcount=483
Regards.
Lineage OS 14.1 & LOS kernel with Magisk 14 does not pass.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
I changed to the v4 extended kernel, Magisk V14.0, and also getting all green on the SafetyCheck with the 35 rom. BUT MagiskHide does not work: when I look at the logs I see
fopen:/magisk/.core/hidelist failed with 2: No such file or directory
Does MagiskHide work for you?
Yes working for me I suspect you have mounting error above that in log?
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
I suggest install stock then extended kernel then magick fresh
snaggletooth1 said:
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
Click to expand...
Click to collapse
Hi, I came from the same video and I did all the steps he put in there. I did the root process with Magisk 13 then I updated to 14 version (a days ago) and everything is working ok.
Hello guys. I need viper4android for CRLI based roms.
I tried magisk's viper but it has driver issue.
I think our new kernel is different. Im not found any selinux permissive custom kernel. I think that driver issue is becouse of selinux enforcing. Can you help me please? Thank you.
ramone01 said:
Hello guys. I need viper4android for CRLI based roms.
I tried magisk's viper but it has driver issue.
I think our new kernel is different. Im not found any selinux permissive custom kernel. I think that driver issue is becouse of selinux enforcing. Can you help me please? Thank you.
Click to expand...
Click to collapse
Go to xda labs search viper4android install the app as normal open it and grant it root then click install driver then reboot. Done works perfectly on my pie rom
Hi, I can not manage to activate viper4android either.
Please help!
I tried giving it root permission but it does not work either.
Check out install driver.
alarcon.gmo said:
Hi, I can not manage to activate viper4android either.
Please help!
I tried giving it root permission but it does not work either.
Check out install driver.
Click to expand...
Click to collapse
Flash Magisk 17.4 in twrp and reboot. Install 2.5 driver, reboot and test it.
If it works go back to twrp and flash Magisk 18, reboot and it should work.
Version 2.6.0.5 is working without any problems. I'm using Magisk v18 and selected Driver version 2.3.4.0
afcaajax said:
Version 2.6.0.5 is working without any problems. I'm using Magisk v18 and selected Driver version 2.3.4.0
Click to expand...
Click to collapse
Thanks, that worke fine !
It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Raven.95 said:
It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Click to expand...
Click to collapse
Shadow 00 said:
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Click to expand...
Click to collapse
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
EdoNINJA93 said:
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
Click to expand...
Click to collapse
Yep, extended kernel do the job too, thanks. So it's really a kernel problem...
Hello everyone,
After a bit of research, I found out that many people with a OnePlus 9 Pro, myself included, struggled with installing viper4android.
Luckily and accidentally I discovered this GitHub repository!
It all works only with a magisk module installation.
After a reboot you're good to go.
I've tested it on Nameless AOSP 13 with SELinux enforcing.
Users have reported incompatibility with OxygenOS.
Nonetheless you can try and see if it works for you.
Cheers!
WOW
It actually worked, what a godsend. Thank you for this kind sir. I've tried so many methods and this is the solution.
I couldn't get it to work on oos13 ...
ffejy462 said:
I couldn't get it to work on oos13 ...
Click to expand...
Click to collapse
Thank you for the info!!
Just switched to nameless from extended. No worky on nameless
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Try with JamesDSP, it usually has fewer compatibility issues and works just as well as V4A.
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Naah... I'm still on Nameless latest version and it's still working. You must be doing something wrong.
Check the repository's instructions again, although I don't think they are difficult to follow, it's just one module to flash... Also make sure you don't have any other audio mods installed. It's okay if you have the built-in Dolby Atmos.
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
tathagatab said:
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
Click to expand...
Click to collapse
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
David_#27 said:
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
Click to expand...
Click to collapse
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
tathagatab said:
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
Click to expand...
Click to collapse
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
David_#27 said:
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
Click to expand...
Click to collapse
As I learned, it doesn't work on OOS 13, irrespective of selinux setting. Or at least I couldn't make it work.
For me it works perfectly, using the Pixel Ex rom. Thank you very much!