Related
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Code:
Installation Instructions
(NOTE: I don't feel comfortable to redistribute SuperSU unless I have explicit permission, so for now, if you want to use SuperSU with Magisk, you are required to have systemless SuperSU installed before flashing Magisk. Magisk will detect SuperSU installation and automatically convert systemless SuperSU into a Magisk Module, using the files that are already installed to your boot image. System installed SuperSU is obviously not supported, since it is not systemless. Actually, it is a trivial task to add official Magisk support to a SuperSU zip package, however the decision is not in my hands.)
If you're rooted with Official Systemless SuperSU, or using Magisk v3+ with Magisk version of phh's superuser
Install the latest Magisk Manager
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, rooted with the depreciated Magisk Version of SuperSU, using Magisk version older than v3, or you got issues when flashing in Magisk Manager (some devices requires Magisk to be flashed in recovery to find boot image location)
(If you have Magisk installed) Flash Magisk Uninstaller to get a clean start
Download the latest Magisk zip file
Download the latest Magisk Version phh superuser from this thread:
[Magisk] [2016.10.4] phh's SuperUser
Flash both zips in custom recovery
Install the latest Magisk Manager for a complete Magisk experience
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
NotExist said:
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
Click to expand...
Click to collapse
Am using an honor 7 PLK-L01 with MM build B370.
Also tried the first method you described with SuperSU 2.62, difference being that magisk manager could not install v7 zip so flashed it manually. It said something about
Insufficient storage for boot image
and kind of aborted.
Since then flashing SuperSU says seplocy failed and aborts.
Tried flashing a new boot and rooting, still the same.
Flashed boot and Cust, the same error both with magisk and SuperSU.
Cleared dalvik and cache, still the same.
Tried the magisk uninstaller, no success...
Would appreciate a solution.
Sent from my PLK-L01 using XDA Labs
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
ibrokemypie said:
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
Click to expand...
Click to collapse
Had to flash system, boot and Cust to root again using SuperSU.
Otherwise it was failing and flashing only boot did not cut the deal.
Sent from my PLK-L01 using XDA Labs
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
HyperCriSiS said:
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
Click to expand...
Click to collapse
Magisk ver 6 works well but have to have that zip and it's corresponding apk I guess 1.2 that is.
Used it a couple of days ways back just to make sure it works.
An update that it works after Magisk v8, although there's no information about it.
(Flash SuperSu v2.65 -> Update to SuperSU v2.78 with Google Play -> update su binary to v2.78 with SuperSU -> install Magisk Manager v2.1 -> Install Magisk v8 with Manager -> done!)
I've had magisk installed since version 6, I've published some magisk modules already and never had a problem until today.
After a full clean reinstall of Nougat NBD90Z (with wipe) on my Nexus 6 and then flashing Magisk, phh's superuser for magisk, installing phh's superuser apk from play store and magisk manager apk I stumbled upon a previously reported (without details) bug where magisk manager would refuse to install modules from repo claiming they are not magisk modules.
I've struggled trying everything I could including the full wipe (more details here: http://forum.xda-developers.com/apps/magisk/module-app-systemizer-t3477512/69230448#69230448) and bounced some ideas off @pnwsr6 who's had the similar problem on Nexus 6 device.
I've achieved a partially working Magisk Manager (manual installs of ZIP files work, but installs from repo still fail) and here's the list of steps which lead to me having semi-working magisk manager again:
1. I flashed ZIP files of some modules in twrp (I'm attaching App Systemizer and Nexus 6 LED Enabler which I flashed)
2. After the phone booted up I saw the modules active and working
3. Within Magisk Manager I then added the ZIP file of the phh's superuser module from that thread (http://forum.xda-developers.com/attachment.php?attachmentid=3893967&d=1475554052)
4. Now at least manual installation of modules within Magisk Manager are working fine.
@topjohnwu -- I've enabled verbose logging and extra logging for bash commands, but I'm still not seeing anything in the log on top of the regular output.
Created an issue against Magisk Manager so it's easier to track for developers: https://github.com/topjohnwu/MagiskManager/issues/20
Looks like that even after flashing some modules in twrp, Magisk Manager only allows to install from zip only exactly the same ZIP I've already flashed (even a minor change and bump of versionCode results in "This ZIP is not a Magisk Module!"). So it might be an issue of Magisk Manager being unable to write to /magisk despite having storage permission and being granted root access.
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
I've seen this error as well on my Nexus 6 NBD90Z with Magisk v8. Started with v7 after some heavy modification on my part .
I was sometimes able to fix it by simply extracting the zip and then Magisk Manager would somehow recognize it as a module.. Other times I could extract the zip and then re-archive the contents and Magisk Manager would recognize that as a module. Weird, but doable.
stangri said:
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
Click to expand...
Click to collapse
I probably won't try again until next update, and hope the wipe just wasn't clearing something. I have the zip installed through twrp and working for now so I'm good till then.
just wondering if you're still having this issue with v9? I had modules installed fine under v6, but never really installed any modules under v8 to see if this problem occurred for me. now that I'm on v9, which has been wiped clean to start, I can no longer install any modules via Downloads or in the Modules section... any suggestions?
I have the same issue when trying to install viper with v9 on Nexus 6P DP2
Skickat från min Nexus 6P via Tapatalk
Same here. Find a fix ?
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
stangri said:
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
Click to expand...
Click to collapse
Just an FYI, I do still have this problem, but can install the zip through twrp. Maybe 10 will be the solution.
I had the same problem, I cleared magisk manager data and it works fine now
Didn't help
Sent from my SM-G532F using Tapatalk
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
stangri said:
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
Click to expand...
Click to collapse
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Meowdib said:
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Click to expand...
Click to collapse
Weird, do you have the same problem with magisk manager 161223?
stangri said:
Weird, do you have the same problem with magisk manager 161223?
Click to expand...
Click to collapse
Same
I need a Help to download modules using magisk
Lastest version, Included phh root, manager is from G. play,
But Modules download function is not working
Say "No modules found" for download to install via magisk.
Canary Magisk Manager: Link
Canary Magisk Manager (Debug): Link
Latest Release Notes: Link
All Canary Files: Link
The Canary Builds are similar to Google Chrome's: bleeding edge of the source.
Be warned: Canary can be unstable.
The binaries from debug channel are built with debug flag ON
Install Canary Magisk Manager and go to Settings > Update Channel and switch to either Canary or Canary (Debug)
If you need a clean start, download the Canary Uninstaller to uninstall any version of Magisk
How to Report:
Only report bugs/logs using the debug channel!!
Magisk installation failure:
In TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
In MagiskManager: Choose to save logs after installation and upload
Magisk bugs:
Magisk logs are placed in /cache/magisk.log (For A/B devices, they are actually in /data/cache/magisk.log)
If you cannot boot or stuck in bootloops, grab logcats (and kernel dmesg if possible) on boot
Magisk Manager bugs:
Grab logcat (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
Ignored
I just installed this on one of my Nextbook Ares 8A's, x86, Android 6.0.1. It was previously on @ianmacd 's unofficial build. So far, it appears to be working great. I un-installed my previous MM, before I install the new one, downloaded the Magisk.zip in MM and flashed it through TWRP.
How much overhead does the extra logging create? I don't notice any difference. Do you think it will affect battery life?
When I check the magisk.log it does appear that it is continuously logging, because each time I check it the time stamp is updated.
If I am not mistaken, on non debug builds the magisk.log is only created at boot and not updated again until next boot?
Thanks, @topjohnwu for creating this new channel for testers.
Wew, downloading and testing on my 7.1.2, so far so good. Thanks.
Aye official snapshots! Awesome. Been using @kantjers up until now. Thanks for this
Sent from my LG Nexus 5X using XDA Labs
Testing now. Thanks ?
No issues with any of my used modules ?
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
Yes, I think Magisk Manager should ask for the storage permission on first launch and not later when the actual storage permission is need. I have been bit by the storage permission a few time in other instances of using MM.
Good find @jcmm11 , I have not used that option to patch the boot.img.
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
This issue is resolved, thank you for your report!
def-g said:
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
Click to expand...
Click to collapse
I'm aware of this issue, will try to figure out the cause of the issue
topjohnwu said:
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
This issue is resolved, thank you for your report!
I'm aware of this issue, will try to figure out the cause of the issue
Click to expand...
Click to collapse
Cool. To be honest, only a minor inconvenience. Your work is greatly appreciated.
I just installed this build and it appears to be fine on my device. The logcat was taken in Logcatx using the per app logcat for Magisk Manager. If you would like a full system logcat, let me know, or if you would like any other info such as last_kmsg or dmsg, let me know.
I have been installing through TWRP, since recently I have twice experienced data corruption issues with the direct install method in unofficial builds, noted in the unofficial thread.
As always, Thanks
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
BustedFly said:
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
Click to expand...
Click to collapse
I suggest you download MM from here and try to install it. I have been flashing Unofficial builds of Magisk for some time and this appears to be a common issue. It should not happen if you did a full wipe of the ROM though.
The latest Canary Magisk Manager.apk download:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/app-full-debug.apk
Direct download for all of the latest Canary builds:
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
BustedFly said:
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
Click to expand...
Click to collapse
By fullwipe, I presume you mean full wipe of the ROM? If not, you must remove the Magisk Manager of the unofficial build before installing this one, as it is signed with a different key.
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
BustedFly said:
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
Click to expand...
Click to collapse
After flashing Magisk and rebooting, the app-full-debug.apk will not install? That is a strange issue. Maybe someone else can help.
On one device with @kantjer 's latest build, I first un-installed his Magisk Manager, installed the app-full-debug.apk, opened it, set up the custom update channel to the link in the op: https://bit.ly/2MPKGY5 and hit install, download Zip only, then rebooted to TWRP and installed that downloaded Magisk.zip and rebooted to a working Magisk install.
Hey @topjohnwu,
I've noticed a line just after rebooting using the Canary:
Code:
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: decode with protobuf from [/data/property/persistent_properties]
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: prop [persist.magisk.hide] does not exist
I'm not sure if it's important or not for magisk functionality, however I wanted to report it just in case something is off.
I'm using OnePlus 6 with Open Beta 2 (Pie, 9.0).
I'm going to make it my duty to delete any and all posts that are not relevent to what the developer wants or is asking for.
I'll be checking this thread daily from here on out. If I find myself deleting a ton of any reoccurring member's posts, I'll be escalating to consequences.
Please, thoroughly give your posts some thought prior to submitting them, and ask yourself if whether or not it fits into how or what the OP is asking.
Thank you
So, tried last canary, nothing critical to report apart that FGO doesn't work (it crashes like before with error 61), here there are both magisk log and catlog.
Catlog (too big for xda, dunno why): https://mega.nz/#!LUoBQY6L!X--KKkCCzQn4SLwaIX1hYsmrKzzNfx1TTSGCh1b-0E4
Magisk log attached.
OnePlus 6 OOS 5.1.11, 8.1 July Patch
If anything else is needed I'll provide it right away
I made the mistake to install Xposed from within the Magisk manager app on my F1.
Now the device hangs because neither the version from magisk nor the current oreo beta3 is compatible with MIUI.
Unfortunately the official xposed uninstall zip can't remove this module and my phone is stuck in the bootscreen.
How can i remove this module or other magisk modules that cause trouble from the shell/twrp so i can boot again?
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
Deleted : @Didgeridoohan 's answer ^ is more complete
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery
Saved my ass by flashing this core-only Magisk boot.img: https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Sorry about thaty @Didgeridoohan was really desperate and freaking out!
@p1r473 The link in post #2 is still valid and has answers for you.
Edit: and it's not that the module is reinstalled. It's there the whole time, but whenever you install a stock boot image Magisk isn't installed and the module won't load. As soon as Magisk is installed, the module will load again and cause problems.
Edit 2: please don't go spamming the same message in several threads. One post is enough... Someone is usually bound to see it.
*Viper4android Pie* Magisk Module
Requirements -
1.Custom Rom (Tested on AEX custom rom for Realme X) Not tested on rooted colorOS6, most probably it won't work because On Color OS, Magisk is working in Core Only Mode so no module works.
2.Root with Magisk v19.4 or v20
3.SELinux Permissive (most custom ROMs already in permissive mode)
4.Busybox
5. Magisk module download from here
https://drive.google.com/file/d/1qSOGFD-X3ULoYiAWZTk-3XZknA8KqDBq/view?usp=drivesdk
Procedure
1. So you are on Custom Rom with TWRP
2. Root with magisk v19.4 or v20.
3. Download Busybox from playstore and install
4. Check SELinux , if its enforcing then set it to permissive using Terminal in TWRP..
Command to set SELinux to permissive => setenforce 0
5. Open Magisk, go to 'Modules' option and add new module by clicking on + icon.. Navigate to your downloaded v4a module, select and install.. (keep your Internet ON during this step).. then Reboot.
6. Enter in V4A, it will ask to install/update driver, install it.. reboot.
7. Viper is ready to bite your ears..
Greetings!
Has anyone got a chance to test viper4android in Color OS 6 after rooting? After the root, we can also directly flash viper.zip from ADB
or from TWRP. Also, after root we can install the app and one gets an option to install the driver. Thank you!
Confirmed. V4a flashed in Rooted realme 3 pro Color os6 not work... Phone booted but black screen. Have some trouble to back to twrp because phone wont turn off. Use volume up and power button phone to force turn off.
Dr.Anshuman said:
*Viper4android Pie* Magisk Module
Requirements -
1.Custom Rom (Tested on AEX custom rom for Realme X) Not tested on rooted colorOS6, most probably it won't work because On Color OS, Magisk is working in Core Only Mode so no module works.
2.Root with Magisk v19.4 or v20
3.SELinux Permissive (most custom ROMs already in permissive mode)
4.Busybox
5. Magisk module download from here
https://drive.google.com/file/d/1qSOGFD-X3ULoYiAWZTk-3XZknA8KqDBq/view?usp=drivesdk
Procedure
1. So you are on Custom Rom with TWRP
2. Root with magisk v19.4 or v20.
3. Download Busybox from playstore and install
4. Check SELinux , if its enforcing then set it to permissive using Terminal in TWRP..
Command to set SELinux to permissive => setenforce 0
5. Open Magisk, go to 'Modules' option and add new module by clicking on + icon.. Navigate to your downloaded v4a module, select and install.. (keep your Internet ON during this step).. then Reboot.
6. Enter in V4A, it will ask to install/update driver, install it.. reboot.
7. Viper is ready to bite your ears..
Click to expand...
Click to collapse
Since when I applied magisk fix... I'm able to use full magisk module.... So thought to give viperfx a try.... But.... It says....unable to mount vendor...
It's Not Working for me..... I'm Using crDroid Rom...Help Me plz....