yashsingh1/xdaforums huggingface dataset:
[Magisk] carlylemiii:
What's your up time? I'm "stock" except ElementalX kernel, TWRP, and Magisk, and mine passes for the first ten minutes or so after boot, and then fails.

Edit: Hmm. Either having too many apps selected for Magisk Hide causes issues, or I had something blocked I shouldn't have, because I unchecked a lot of apps I had selected, and now things seem okay.
[Magisk] mmad81:
Running PN on Pixel XL, safety net passes but I can't get any modules to stick that were working on 14.2
[Magisk] negroxxx:
excellent work
[Magisk] SpasilliumNexus:
All good so far on OnePlus 3T with AOSPA 7.3.0.
[Magisk] Nevermindthelabel:
OnePlus 3 OB25 unable to boot. Unfortunately no magisk_debug.log this time, and it happens before boot so I can't get anything in adb either. Only thing i could find that may be of help was stock boot backup in /data. Stock boot img and backup https://drive.google.com/open?id=0B-nfE8YlFQ6PZFU4UUExSGZnTTg
[Magisk] dugi9991:
All fine on latest DU, OP3
[Magisk] DynamicDonkey:
How do I go about installing this? I have 14.2 installed already. Do I need to uninstall first or can I just flash directly over it in TWRP? I'm on Pixel Oreo with iYTB module.
[Magisk] precompiled:
Unfortunately 14.3 still produces a bootloop on the Mi A1.
[Magisk] nycdiplomat:
Uptime is about an hour And counting. Running elemental as well with TWRP. Just ran it again and still passing.
[Magisk] dugi9991:
I've installed it through the app, after it notified me off an update. Also using the iYTBP module, everything working fine after the reboot, without re-installing the module.
[Magisk] Orka82:
Edit: To much trouble. Don't do it. Wait for official release. ;)
[Magisk] Soooperstar:
Has anyone tried restoring with Titanium backup on 14.3
[Magisk] DynamicDonkey:
It can be installed through the app? It wants me to install 14.0 in the app.

EDIT: had to enable beta channel in the settings. Thanks!
[Magisk] DynamicDonkey:
SafetyNet working as well.
[Magisk] kokesh:
What phone/OS?

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

There is already Oreo compatible TWRP. Works great!
[Magisk] Orka82:
TWRP is not a problem. It has been working fine for me.

Where could the "compatible" version be found? :)
[Magisk] Nevermindthelabel:
Won't you bootloop unless you are able to run the command again? Not to mention possible security issues with permissive.
[Magisk] Orka82:
No, just need to run once.

And yes, probably eventually a security issue but I think I know what I'm doing (and the phone is running Magisk? hehe) and as I said "I see this as temporary workaround." ;)
[Magisk] Yourboymusti:
Hello, I've lost root when installing v14.3.

Can someone help me out please?

Note 4.

7.1.2

Resurrection ROM

With USNF
[Magisk] chazarss:
Hi all,

Main thread says that latest stable magisk is 14.3 but app can't find it and also download link on thread gives 14.0, so what wrong anyone knows?
[Magisk] Captain_Throwback:
No, it doesn't. Stable release is still at 14.0.
[Magisk] kishd:
14.3 is still beta. Last stable release is 14.0. enable beta channel in Magisk manager to test 14.3
[Magisk] lekiaM:
OnePlus 5, LOS based custom Rom android 7.1.2
[Magisk] jenslody:
It's beta not stable, you have to switch to beta-channel in MagiskManager settings therefore.
[Magisk] Nevermindthelabel:
If you look closely at that post it says 14.3 is a beta
[Magisk] Francescoso:
Works Magisk v14.3 on Oneplus 3 beta25 Oreo?
[Magisk] mrkrazy:
Just wanted to share that Magisk and SafetyNet are working flawlessly for the first time on my Find 7A with OMNI ROM running Oreo :)

A huge thanks to to developer on a amazing job with this tool!
[Magisk] n0j0e:
Minor issue...

Hi, after some 14.x updates i have something like this in my modules list:

(see attachment)

Also with modules.prop & update.

Deactivating or deleting doesn't help. After reboot these are back and activated again.

Send with much love & Android.
[Magisk] anderskaseorg:
Nexus 5X with FBE hangs during boot animation

I installed Magisk v14.3(1437) on a Nexus 5X (Oreo OPR4.170623.009, Oct 2017) with file-based encryption (requires twrp-bullhead-fbe.zip from https://github.com/TeamWin/Team-Win-Recovery-Project/issues/854#issuecomment-326738803), but it hangs during the boot animation.

Logs:

magisk.log: https://paste.ee/r/Midw4/0

magisk_debug.log: https://paste.ee/r/Midw4/1
[Magisk] jenslody:
You most likely have a file named "auto_mount" in "/magisk".

Either remove it from a terminal-emulator, while your device is running and reboot afterwards, or boot into custom-recovery and mount "/data/magisk.img" by flashing "Mount Magisk" from this thread, remove the file and reboot.
[Magisk] demonoidmaster:
Sweet delicious logs

---------- Post added at 12:38 AM ---------- Previous post was at 12:31 AM ----------

People shouldn't use Stericson's busybox, besides most recent busybox is 1.26.2 why are you posting such an old build of it? Anyways jrummy's busybox has never caused any issues so I'd recommend either using that or another up to date busybox
[Magisk] ryaniskira:
Modules don't seem to be installing on 14.3 beta. Google Pixel XL, Pure Nexus 7.1.2 July. They go through and run their script, but upon reboot they don't actually show up as installed nor function. This is all that shows up in the log: https://pastebin.com/kA93dVXA
[Magisk] demonoidmaster:
Nobody cares, read the fine print in the op about safetynet and magiskhide
[Magisk] ryaniskira:
Do you have an A/B device like the Moto Z2 Force or Pixel? Module installs are not working for me.
[Magisk] psychoela:
tester 14.1 and 14.2 result always bootloap,but with 14.3 now is working just fine,yeahhh:victory: Is anyone have same issue like me, better try 14.3:)
[Magisk] casouzaj:
Version 14.3, just like all the previous ones, is working great in my Sony Xperia Z3 Compact (D5833 variant), running the latest CarbonROM release. Thanks a lot!
[Magisk] fOmey:
Doogee MIX : Mediatek MT6757

Unfortunately still seem to be having issues on 14.3..

Magisk.log

Magisk_debug.log
[Magisk] Orka82:
Found it in the release thread in the OnePlus forum. Now I can flash without modify the zip. Thanks for mention it.

I also removed my post about how to make Magisk work on oneplus 3. Had too much problems with it so don't do it. :eek:
[Magisk] rsm23:
It Does not work on my Oneplus 3 after the latest beta Release V25
[Magisk] L.F.B.:
Sky is the limit for the master johnwu...

Its amazing what magisk is... An incredible tool... Never made before in android world.

Thank you master [MENTION=4470081]topjohnwu[/MENTION] ???
[Magisk] L.F.B.:
Delete duplicated.
[Magisk] Tkbf:
My device running v14.2 pretty well until upgrading to v14.3(1437) via TWRP, I got boot-loop in new version, debug log as attached.

Flash back to v14.2 but still boot-loop, so finally flash Magisk-uninstaller.

After clear things up, flash v14.3 again, this time it installed successfully.

Edit:

While v14.3 running, trying to install Xposed module (88.1 sdk24) in Magisk Manager 5.4.0, initial installation show it is done successfully, but module didn't show up in Manager after the reboot. Then I install Xposed module again in the Manager, this time it present installation failed (screen snapshot as attached), then I encounter system crash (force reboot), and got boot-loop again.
[Magisk] simar404:
Guys stop usimg twrp while flashing magisk, instead use flashfire

1. Open magisk manager and click on uninstall and then click on restore stock boot.

2. Just simply select magisk zip to flash from flashfire and disable auto mount (only for non pixel phones), disable everoot. (if it is enabled it will install super su)

Enjoy
[Magisk] r.Ry4N.05:
I always flash Magisk and the modules in TWRP, and I never had any problems.
[Magisk] simar404:
Good but its fr those who are facing problems through twrp

However can u solve this:

I can't install busybox because it says free space unavailable for system/xbin. Its in busybox free installer app when i open it, if i click on install, it always says busybox installation unsuccessful

Any help would be appreciated
[Magisk] Tkbf:
All right, so I have another story to tell, somehow still a little bit strange...

I start clean by flash uninstaller, then flash back to v14.2, everything is OK, including Magisk Xposed 88.1 and all modules of Magisk and Xposed.

When Magisk Manger 5.3.5 prompt me to upgrade to 5.4.0, I agree, and it installed successfully.

Following the new Manager prompt me again this time asking to upgarde Magisk v14.3, I agree, too. Installation is successful surprisingly no boot-loop!! (Last time I was using TWRP rather than the Magisk Manager)

OK, so running Magisk v.14.3 within Manager 5.4.0, I install Magisk Xposed 88.1 SDK24, it is done and everything is OK, all my Xposed modules are working too.

Then at some point I got system crash again suddenly , and then stucking on boot logo, but long pressing power button to force device to reboot will boot to desktop like normal. Then I got another system crash and force reboot a few minute later.

Will roll back to v14.2 temporarily until thing get more clear.
[Magisk] anderskaseorg:
FlashFire needs root, so it doesn’t help if I’m trying to gain root in the first place. Besides, I’d prefer to avoid using closed-source software as root. The main thread says to use a custom recovery, so I don’t see why TWRP shouldn’t work.
[Magisk] demonoidmaster:
Did you grant it root?

---------- Post added at 05:20 AM ---------- Previous post was at 05:19 AM ----------

I'll have you know FlashFire is made by Chainfire.. Yknow, the guy who made SuperSU?

---------- Post added at 05:25 AM ---------- Previous post was at 05:20 AM ----------

*sighs* why did you install an inferior versioned magisk manager? You went from using the v3.5.8 manager (tf, current manager is 5.3.5) to 3.4.0 when the newest manager is v5.4.0

Anyways no matter what version of magisk you're running, it's always better to have the latest manager than not, so js there was nothing wrong with your magisk install, you should've just uninstalled the app and installed the one bundled in the 14.3 zip
[Magisk] mandarpalshikar:
How to install on OOS Beta 16 with SuperSU installed with TWRP

Hey guys, can someone please help getting exact steps and zips to install on Op3T OOS Beta 16 (Oreo) with SuperSU installed and with TWRP recovery?

If I try to install 14.3 magisk zip it gives me boot image error.
[Magisk] husseinaltaaf:
Hello i am currnently On Magisk v14.2 How should i update To v14.3? Should i Just Download The zip File and Flash It or.....?
[Magisk] simar404:
Yes i granted it root, currently running magisk 14.3
[Magisk] laupuy:
Hi,

1- Off topic, please read OP

2- After-sales service is closed on Sunday, please come back on Monday or call the emergency at 911

3- Do your homework: read, search and learn

4- Because of points 1, 2 and 3, I'm afraid that manipulation (already given a few pages before) is too complicated for you, sorry

have a good day
[Magisk] Tkbf:
Sorry, that was my big typos.

Actually I was upgraded from 5.3.5 to 5.4.0, I confirm that afterward.
[Magisk] neilbangs19:
OnePlus 3 Open Beta Oreo build does not support magisk

Here is the stock boot image file please add support for it

https://drive.google.com/file/d/0B-F4LFOP2fPcalpFQmJiUkxjY28/view?usp=drivesdk
[Magisk] r.Ry4N.05:
Are you using the BusyBox app by Stericson? I never had problems with that too. Maybe you can try another BusyBox, perhaps the systemless one by osm0sis for Magisk?
[Magisk] manishmehra373@gmail.com:
After updating to latest magisk manager

It keeps force stopping.

I am unable to use it.

Tried re flashing magisk.clear cache but non is working.

How to revert to old magisk manager 5.30
[Magisk] demonoidmaster:
Just upgraded from v14.2 to 14.3, no issues
[Magisk] Tkbf:
You might try to clear data of the manager app.

To revert back to old manager, you can flash old ver of Magisk, it has bundled with corresponding manager app, e.g. Magisk V14.2 with 5.3.5, V14.3 with 5.4.0.
[Magisk] demonoidmaster:
He should just clear the app data, uninstall it then install the apk again
[Magisk] Tkbf:
Good to know there is no issue on your side, may be my device using non-standard boot image formats.
[Magisk] Didgeridoohan:
Mi A1 support is being worked on. It's a tricky device...

The magisk_debug.log from /data might show more. Save it after installing a module and rebooting.

Logs? Instructions in the OP.

I don't think there's been any work on that just yet..

Grab a logcat from the crash.

When installing Magisk for the first time you can use the recoveryless installation. Let the Manager patch the boot image and flash it to your device manually. Instructions are found in the release thread.

To install Magisk, you'll first need to completely remove SuperSU. There's a troubleshooting guide stickied at the top of the forums. It's a pretty good read, if I may say so... :D

But! OnePlus have done something to the Oreo beta that causes bootloops with Magisk... Go back to Nougat, for now, if you want to use Magisk.

Clear data for the Manager, not just cache.
[Magisk] Eduardo379:
Magisk is showing the notification to install the new manager but when I tap it nothing happens, what to do ?
[Magisk] mandarpalshikar:
Thanks for info. I guess we will need to wait till someone comes up with magisk for OOS Beta 16.

I know this maybe off topic. But I needed magisk only for viper4android. Is there a known way of having viper4android working on Oreo? Official thread says it's supported only till Android 7. No explicit mention of 8.0
[Magisk] akboy7015:
Hi,

I don't know if you are in charge of translations, but I have a small mistake in French translation: "chosiir" instead of "choisir" in settings page (see screenshot)
[Magisk] ryaniskira:
https://pastebin.com/13QmfkjY
[Magisk] paed808:
14.3 seems to have fixed the "root loss" issue for me on my Moto G 2014 running Lineage OS.
[Magisk] lssong99:
Yes, I have exactly issue like yours. My Asus zenphone 3 Deluxe runs 14.2 and Xposed module 88.1 (installed from Magical depo) normally but after upgrade to 14.3 (Magisk Manager also being upgraded), the system had following issues:

1. Very long boot up time and after boot up, Xposed frameworks stopped working . Reinstalled Xposed framework 88.1 from within Magisk Manager fixed this issue.

2. After normal boot up, the system will crash spontaneously (I didn't touch the phone) and reboot. This reboot took long time. I end up force (volume+pwr key) restart the phone, clean Davlik and cache and the phone will boot. However it will again crash after maybe 3~5 minutes.

3. I end up return to Magisk 14.2 (Magisk Manager still keep at 5.4.0) and reinstall Xposed 88.1 then everything back to normal...

I didn't found any log since with all those reinstall, it might be gone somewhere...
[Magisk] lekiaM:
Del (forgot to quote)
[Magisk] andynx1:
Moto G5+, LOS15.

14.3 installed OK through TWRP (wouldn't install from within the app). But loss of root.

Back on 14.2, working fine.
[Magisk] lekiaM:
Nope. OP5, Arm64. Running Palm Rom with some personal tweaks and optimizations from the Dev in question. Based on the latest 14.1 LOS sources for cheeseburger. Also I'm not running Xposed or any other Mods that can (IMO) interfere with Magisk and their Modules. ?
[Magisk] Tkbf:
What kind of log should I get at that stage? Thank you.
[Magisk] iruleshtar:
After reading some bootloop comment... I forget how to update the magisk?

Im on 14.20 with RR 5.8.5
[Magisk] oTeMpLo:
Magisk manager 5.4.0 wont start. Op3t oos4.5.0
[Magisk] alexdpaul:
How did you roll back to 14.2?
[Magisk] andynx1:
OK, I had the 14.2 zip on my phone.

I booted to TWRP, wiped (just) both caches - not a full wipe. Then re-flashed my ROM, gapps, 14.2 and the fix.

Back on 14.2, all good.
[Magisk] JERW28:
I personally flash my boot.img in twrp before flashing each bata to make sure there are no conflicts between bata builds. Others dirty flash one build over the last and it works fine for them. It's your choice. But if you are having issues definitly flash a clean boot.img before reporting a bug.
[Magisk] aamadorj:
This is what happen when I run "dumpsys batterystats --reset" at an elevated terminal, according to the logcat:

[ 06-12 19:54:21.837 19200:19200 W/dumpsys ]
type=1400 audit(0.0:67): avc: denied { write } for path="pipe:[107864]" dev="pipefs" ino=107864 scontext=u:r:system_server:s0 tcontext=u:r:su:s0 tclass=fifo_file permissive=0

I installed the newest Magisk v13 beta before running the command. I can provide more information or a entire logcat in case it's needed.
[Magisk] trader418:
Go into magisk settings and enable magisk hide, try to pass safety net again, does this not work for you?
[Magisk] demonoidmaster:
Apk in the zip was a placeholder that would direct you to the Play Store but now Magisk was pulled by Google so only way to get the manager is by going to Apkmirror (god bless that divine website) and searching for it (v5.0.0)

---------- Post added at 03:51 AM ---------- Previous post was at 03:50 AM ----------

Never had issues flashing SuperSU or Magisk with 3.1.1-0

---------- Post added at 03:55 AM ---------- Previous post was at 03:51 AM ----------

Magisk manager isn't bundled with the zip, only apk it has is a redirecting placeholder executable apk app that brings you to the Play Store (Magisk was removed from it, use Apkmirror instead, find Magisk v5.0.0)

---------- Post added at 03:56 AM ---------- Previous post was at 03:55 AM ----------

Try clearing out the concour apps data then reboot
[Magisk] :
[MENTION=7086291]demonoidmaster[/MENTION]

A bit off topic, but just so you can see:

https://xdaforums.com/samsung-a-series-2017/development/xcc-t3591448

No users of this device specifically can flash SuperSU with TWRP, and I guess it's affecting Magisk's beta too, problems of a similar source, I'd guess, which might be resolved when v13 gets to its stable release.

Only Magisk v12 succeeds with 3.1.0-1 and Xposed by Wanam, and all the uninstallers (un-SU, Magisk and Xposed).
[Magisk] syamsoul:
just install the apk which exist common folder. no need to go to apkmirror.

but according to install script, i believe it should install the magisk manager while flashing the zip.
[Magisk] Didgeridoohan:
Sorry! I'm a bit late to the party... Didn't get a hold of my test device until late last night and then life happened and know I'm back. :D

On my Nexus 6 with Vanilla ROM 7.1.2_r14, TWRP 3.1.1-0, I still get CANNOT LINK EXECUTABLE (log and boot image attached). Clean flashed, tried an earlier version of TWRP, no luck.

The new beta flashes perfectly fine on Pure Nexus 7.1.2_r8 though, so there seems to be some issue with the kernel in Vanilla, by [MENTION=6842057]The Flash[/MENTION].

Was gonna try a stock factory image as well, but like I said, life happened and I won't be able to do that for another 24 hours or so.

Seems like I'm a minority here though and that things are going in the right direction. :good:
[Magisk] Didgeridoohan:
From Magisk v13 the Manager is bundled inside the zip. No need to go looking for it outside xda.
[Magisk] nathanchance:
I'll try to take a look at this later tonight.
[Magisk] Shen Ron:
Flashed with no problems and magisk.img was present but rebooted and the app showed that magisk was not installed even though I flashed it over V12.
[Magisk] demonoidmaster:
No that's a 45kb apk, version: stub

Proper apk is about 11mb and version 4.3.3 (sorry i didn't know he bundled the apk in v13, current version that i have v12 has a stub apk in it)

---------- Post added at 05:22 AM ---------- Previous post was at 05:20 AM ----------

Ah so he actually bundled it in v13

I was referring to v12 (what I'm currently running) because this current stabe version has a stub apk instead of the full thing, but ok then lol, i didn't know he put it in
[Magisk] Didgeridoohan:
You're posting in the beta v13 thread... If you haven't got the facts straight you're just gonna create confusion.
[Magisk] nugroho2:
Just info: install the latest version 1e87780 on Redmi 3X, Miui 8.7.6.5 global beta, MM. Run smoothly on the first flash/install... Has anybody on Miui tried to install xposed with this Magisk 13?
[Magisk] jenslody:
SM-J500FN DBT latest stock

was booted before with SuperSU and later with Magisk v12 and unofficial v13 from stangri.

1e87780 can not be flashed with TWRP, due to incorrectly detecting my phone as 64-bit.

/system/lib64 exists and so the path and LD_LIBRARY_PATH get set incorrectly.

I don't know where this comes from, content is:

root@j5nlte:/ # ls -l /system/lib64/
-rw-r--r-- root root 452552 2008-12-31 16:00 libSecMMCodec.so

After commenting out the lines where the 64-bit folders are used for ENV in update_binary and boot_patch.sh I can flash Magisk, but MagiskManager does not detect root or even see MagiskSU.

su can not be found from adb shell, but log contains nothing related to su or magisk.

su exists in /sbin_orig as symlink to /sbin/magisk, which does not exist.
[Magisk] DodoGTA:
Your phone's CPU (Snapdragon 410) is 64-bit
[Magisk] SDMU:
Will version 13 make it much more easier for developers to develop modules as compared to the previous versions ?
[Magisk] dreinulldrei:
Same here on OP3T with Open Beta 8 (7.1.1).
[Magisk] kartikb:
Hi [MENTION=4470081]topjohnwu[/MENTION]

I have a Pixel XL now? Is there any way I can flash this or help in testing on it?
[Magisk] heri1978:
I thought, beta version will be more complicated, but it not, work perfectly compare V12. No issue so far....:good:

Samsung GT-I9205 meliustexx.

RROS 7.1.2. Official.
[Magisk] Owls:
Latest beta, pin still broken. Huawei P9 Lite, android 7.0, C10B380.
[Magisk] ves626:
I've found a way to get last kernel log(Android 6.0+ - /sys/fs/pstore/console-ramoops)

I'm attaching here Mi A1 kernel log with Magisk v14.3 bootloop, if that could help somehow...

Unfortunately even in v14.3 there are no logs in /data/
[Magisk] gaja22:
Force close with Magisk Manager 5.4.0 with OOS Oneplus 5 and Pure Fusion ROM. Trying to get back to 5.3.0.
[Magisk] wartomato:
Everything okay on my OnePlus5 running LOS-based AICP n7.1.

No root loss, modules install fine, syszemless hosts, etc.

...so, like always Good Job! :good:
[Magisk] bountyman334:
This worked for LG V20 7.0 h91810k running stock. Thanks bud.Your really a mad genius :good::good::good:
[Magisk] Akshay_1993:
Hi,

I have recently rooted my phone with magisk manager.

After rooting device i found that it is not promiting grant/deny root permission dialog and also it is not showing application in superuser of magisk manager.

Other details :

Phone : Coolpad Note 3

Device : CP8676_I02

OS : Android 5.1

Magisk Manager : 5.4

Magisk Root : V14.3 / also tried V14.0

Log :

E/Magisk (22620): select failed with 2: No such file or directory

W/Magisk (22620): su: request rejected (10355->0)

E/Magisk (22644): select failed with 2: No such file or directory

W/Magisk (22644): su: request rejected (10355->0)
[Magisk] kroening.s:
I have that problem often too, for me it gets fixed by dirty flashing Magisk with TWRP
[Magisk] Akshay_1993:
Can you guide me for this so i can keep magisk as root. Else I have to install King root.
[Magisk] kroening.s:
You said you did root with Magisk 14.3.

Now go to your recovery with that you flashed Magisk already before.

In recovery you flash the magisk 14.3.zip (or whatever the name is). After that you reboot and everything should work again. :good:

If you installed Magisk with Kingroot and not custom recovery, then go into your Magisk Manager and tap on install/update and in the pop-up that should appear to also on install.

Let it do its thing and tap on restart after finish. :good:
[Magisk] jenslody:
This might well be a magiskhide issue.

Can you test if it works, with some kind of root-checker (rootbeer-sample or similar) ?

Or from a terminal-emulator or from adb shell ? As root type "magiskhide --ls" and see if it is enabled.
[Magisk] Akshay_1993:
I did it as you said to go to recovery mode with twrp and install magiak14.3.zip but still not working. I do not have customer rom or king root in device.
[Magisk] onesolo:
Can we see a fix to Seqr?! Still not working on latest magisk 14.3 beta...