yashsingh1/xdaforums huggingface dataset:
[Magisk] Wolfcity:
Updated Magisk Manager, installed Magisk directly through the app, rebooted and everything was fine again.

Magisk root is working,my modules too and yes,if I want to I can pass sn.;)

Good job [MENTION=4470081]topjohnwu[/MENTION] !
[Magisk] VDDZ:
Chuwi Hi8Pro

Having issues with the latest uninstaller, it's not finding my boot image. The uninstaller and installers have been hit or miss for me, does anyone have a uninstaller from June? Think that one was working for me, Magisk 13.3 was ok, no module support and magiskhide couldn't make or write to the .core/hidelist. I'm on a chuwi hi8pro
[Magisk] stangri:
Magisk-ized Pixel Launcher leaked earlier today is attached.

Maybe because I've had Nexus Launcher installed previously or due to some other reason I didn't get asked to pick default launcher after install, so I've just started the Pixel Launcher with:

adb shell am start -n com.google.android.apps.nexuslauncher/com.google.android.apps.nexuslauncher.NexusLauncherActivity
[Magisk] JudgeDread11:
Phh's superuser doesn't require selinux to be permissive.
[Magisk] jsaxon2:
Tried it, but it didn't work for me. I have the PixelLauncher folder in /magisk but can't find the launcher. I tried the command you posted but didn't help.
[Magisk] shindatuin:
Sorry guys! I thought it was a quick reply..

Anyway i've managed to make it work..

I guess the xposed framework here doesn't support my miui 7 5.0.2?

I'll try some tweaks hoping it works
[Magisk] RandomPooka:
Entirely unnecessary to quote the entire (lengthy) OP when saying "It doesn't work", and then not providing any logs from the system or from recovery.
[Magisk] stangri:
I got mine working, so can you try this one please?
[Magisk] Aakash Kaushal:
Idk why the magisk toggle remains off even after turning on...i tried to turn it on many times but it always revert back to off though magisk works perfect..any solution?
[Magisk] cire27rn:
Hi. Anyone experiencing no deep sleep? I had a massive batt drain overnight and it is idle. No 3g and no wifi. I think phh super su is causing this
[Magisk] alroger:
Works for me. :D Thanks.

Send it to the modules thread!
[Magisk] singsic102:
So it could be installed on MTK Phones? Please I need to install it in MYPHONE my33....
[Magisk] chris900:
Also I have the same problem...... :( :( :( :( :( :(

something relating to boot image?? :confused:
[Magisk] lordnakki:
I have same issues on my moto x 2013. I have also tried with AICP without luck :( i hope they fix it asap
[Magisk] Temptasian24:
If I full unroot and install magisk, will my phone go back to stock or will my phone still have my current rom and all my apps and contacts?
[Magisk] anshsharma123:
Did you cleanly uninstalled any previous xposed and flashed the xposed 86.5 sdk23 systemless zip?
[Magisk] hgoldner:
Unrooting and starting the PROPER process of moving towards Magisk, root, and, if desired, Xposed has nothing to do with your apps and contacts. No full wipe is required, and wipes of cache or dalvik have no effect either.
[Magisk] B6000man:
I am using magisk v6 in l720t galaxy s4 phone and the magisk manager 1.2 will not install it keeps saying binary is not found in the zip file in twrp? Also I installed the magisk viper4android in twrp and I do not see it in the list of apps?
[Magisk] hokey10:
edit: problem fixed
[Magisk] iamaniff:
Will PG work with xposed by Topjohwu?
[Magisk] Äptiva:
So here's my issue. I have a LG G2 (ATT) and of course my bootloader is locked and no method to unlock it. Now that being said, our kernels, recoveries, etc have to be bumped. Is it possible using recovery and adb to pull the boot image after the patches are applied bump it, and then reflash it via dd?

Edit:

After some tinkering I managed to get this working in CM13 with some added steps. The purpose I installed it was for PoGo, but it still maintains that I cannot play. I will be looking into it more for this reason.
[Magisk] Eneco:
That's the version available on FDroid I think. Still can't get it to work.

Yeah, sorry, you're right.

I'm using a Nexus 6P, deodexed N stock rom (NRD90M) with latest Magisk, pph's Superuser and AdAway (3.1.2).

So I installed Magisk and root is working fine, but AdAway just doesn't, which means it tells me it's activated, but there are still ads everywhere even after a reboot. I tried setting /system/etc/hosts and /magisk/.core/hosts, but both files do nothing (for the latter AdAway also tells me there is a missing symlink, but from what I read it should just work with the default system hosts file).

It was working without a problem before with just SuperSU installed.
[Magisk] ascii024:
I pass the safety check with no problems with 13.3 (I just Installed 14.0 and still all good)
[Magisk] k0m3n9:
Good to hear that.. Did u install systemless xposed framework?
[Magisk] ascii024:
No, I did not, I'm actually looking at the thread cause I saw that name alongside Magisk, didn't knew that it was a module for it. Going to install it and report later.

EDIT: I was able to install Xposed, now the safety check gives me a false status and I'm still unable to open the app.
[Magisk] Taverius:
My Moto Z (AOKP) updated fine.

My Galaxy Tab S2 (Lineage) is bricked. I can't even get into recovery to flash something - it freezes at the Samsung screen.

Help?
[Magisk] k0m3n9:
Safety net passed on LOS 14.1 KLTE.. But without sussessfully install systemless xposed framework.

To those who stuck at boot after upgrade to magisk 14.. try clean install magisk 14 ie. uninstall & reinstall magisk 14 via TWRP.

To me it stuck at boot after installing systemless xposed sdk 25 whether from Magisk 14 downloadable module or from ver built by purifyOS.

---------- Post added at 08:10 AM ---------- Previous post was at 07:57 AM ----------

Your problem actually same as mine.. only that I'm running LOS on galaxy S5. Idk how to manually enter recovery on Tab S2 coz on S5 i just need to remove the batt once it stuck at samsung bootlogo. Try force shutdown your Tab S2 (does the batt removable?.. idk) then manually enter recovery & clean install Magisk. This will uninstall all previously installed Magisk modules. So far i found the boot stuck caused by systemless xposed module.
[Magisk] Taverius:
I guess its removable if I get some tools and open it up. :(

It has the same modules as my Moto Z - App Systemyzer, GMS, F-Droid Priviledged, Greenify.

Moto Z boots, the Tab S2 won't.

At this point, with how little I'm getting out of it and how often it gives me issues, I'll uninstall for good, I think. :p

Anyway, I guess I'll let it full discharge on its own.
[Magisk] k0m3n9:
This was the same to me with Magisk 13.3. previously. Systemless xposed on magisk will break the safetynet pass no matter what.

The only difference now I still got boot stuck after installing systemless xposed sdk 25. Are you on stock Noughat?

---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------

No Xposed framework installed?
[Magisk] Taverius:
Not since the latest factory reset and clean flash, no, so there's really nothing which should be breaking me, let alone preventing me from getting into TWRP.

But apparently there is, and it does.
[Magisk] ascii024:
I'm on LineageOS latest version (09/04), no custom anything, I guess the only custom thing I've installed is Magisk and Xposed SDK25.
[Magisk] xNotta:
I updated to Magisk 14.0 after using the Uninstaller.

My boot times are about 10-15 minutes. When I install any module I bootloop.

Went back to 13.3 and had a maybe 1 minute tops boot time and module installation works fine.

I used existing modules and made my own template from v4 and v1400 to test and v14.0 bootlooped every time any module installed.

Also did an uninstall with a /system, /cache, dalvik wipe before reinstalling.

I don't know what's up but 14.0 has been terrible for me. Could it be my dirty /data flashing?

Nexus 6, 7.1.2, NitrogenOS, stock or fk kernel r71, Magisk 13.3 or 14.0. (sorry about no logs, my phone has been down since this afternoon today due to 14.0 bootloops.)
[Magisk] dimm0k:
running fine with 13.3, but updated to 14.0 by uninstalling 13.3, installing fresh boot.img, and then installing 14.0. everything works with no modules installed. after installing any module, I just get stuck at the LG boot logo on my LGV20. looking in the magisk.log, I see the following at the end

D( 479: 705) resetprop: prop [persist.magisk.hide] does not exist
I( 479: 731) * Starting MagiskHide
D( 479: 731) resetprop: deleteprop [persist.magisk.hide]
D( 479: 731) resetprop: delete prop: [persist.magisk.hide] error
I( 479: 731) hide_utils: Hiding sensitive props
D( 479: 731) resetprop: getprop [ro.boot.verifiedbootstate]: [orange]
D( 479: 731) resetprop: setprop [ro.boot.verifiedbootstate]: [green] by modifing prop data structure
D( 479: 731) resetprop: getprop [ro.boot.flash.locked]: [0]
D( 479: 731) resetprop: setprop [ro.boot.flash.locked]: [1] by modifing prop data structure
D( 479: 731) resetprop: getprop [ro.boot.veritymode]: [enforcing]
D( 479: 731) resetprop: prop [ro.boot.warranty_bit] does not exist
D( 479: 731) resetprop: prop [ro.warranty_bit] does not exist
D( 479: 731) resetprop: getprop [ro.debuggable]: [0]
D( 479: 731) resetprop: getprop [ro.secure]: [1]
D( 479: 731) resetprop: getprop [ro.build.type]: [user]
D( 479: 731) resetprop: getprop [ro.build.tags]: [release-keys]
D( 479: 731) resetprop: prop [ro.build.selinux] does not exist
D( 479: 731) hide_list: initialize...
I( 479: 731) hide_list: [com.google.android.gms.unstable]
I( 479: 731) proc_monitor: init ns=mnt:[4026531840]
--------- beginning of crash
I( 479: 934) ** late_start service mode running
I( 479: 934) * Running service.d scripts
I( 479: 934) * Running module service scripts
I( 479: 731) proc_monitor: zygote ns=mnt:[4026534377] zygote64 ns=mnt:[4026534378]

any suggestions?
[Magisk] lu4414:
Can someone please refer to. an tutorial on installing Magisk trough ADB? How to load it to device once it's generated on Magisk Manager especificallyy?

Best regards

Sent from my Nexus 6P
[Magisk] arrrgh:
I'm having problems installing modules after the update.

E( 4692: 6836) MANAGERERROR: ProcessRepoZip: Error!

Happens when downloading directly and as well when flashing local zip. Tried a few different ones to make sure it wasn't corrupted dl.

Edit: Looks like MagiskManager couldn't find the file based on logcat. After manually creating the MagiskManager folder everything is working- I think previous versions of MagiskManager automatically created the dl folder but this is not working for me in the latest Manager.
[Magisk] JohnHorus:
"Magisk-vnull.zip"

When updating to v14, I was also prompted to install "Magisk-vnull.zip." Any idea what that was?

I was prompted to update to client 5.3 first, but that install failed because I forgot to toggle unknown apps, so it may just be a bug in the older client?
[Magisk] Chocklety Boyee:
Plz nodify for nougat and make it compatible..
[Magisk] MardKhubHast:
I can't get Magisk Manger to install it on LGv20, T-mobile. I downloaded a stock V20 bootloader zip file, which has an aboot.img file inside of it. In magisk manager, when installing, I select for patched boot img, select the aboot.img file, and I get an error stating "Sony Elf32 format detected. Please Use Boot Bridge to flash Magisk. Failed!". Can anyone provide help? Thanks.
[Magisk] k0m3n9:
I just revert back to Magisk 13.3.. Something missing i noticed when installing v14.. v13.3 have this two lines during installation :

"Creating /data/magisk.img"

"Mounting /data/magisk.img to /magisk"

I've no idea tho....

Or maybe v14 still require us to flash stock boot image as stated in the Installation Instruction. Can someone please clarify this.
[Magisk] XyByDy:
No it doesn't work. I rebooted the device here's the new log. Could the problem be the line about permissive?

Here's the new log

--------- beginning of main

I( 2627: 2627) Magisk v14.0(1400) daemon started

I( 2627: 2629) ** post-fs mode running

--------- beginning of system

I( 2627: 2653) ** post-fs-data mode running

I( 2627: 2653) * Mounting mirrors

I( 2627: 2653) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system

I( 2627: 2653) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 2627: 2653) bind_mount: /dev/magisk/mirror/bin

I( 2627: 2653) * Mounting /data/magisk.img

I( 2627: 2653) * Running post-fs-data.d scripts

I( 2627: 2653) * Enabling systemless hosts file support

I( 2627: 2653) bind_mount: /system/etc/hosts

I( 2627: 2664) * Starting MagiskHide

I( 2627: 2664) hide_utils: Hiding sensitive props

I( 2627: 2664) hide_list: [com.google.android.gms.unstable]

I( 2627: 2664) proc_monitor: init ns=mnt:[4026531840]

I( 2627: 3086) ** late_start service mode running

I( 2627: 3086) * Running service.d scripts

I( 2627: 2664) proc_monitor: zygote ns=mnt:[4026534242] zygote64 ns=mnt:[4026534241]

I( 2627: 2664) proc_monitor: com.google.android.gms.unstable (PID=5905 ns=mnt:[4026534383])

I( 5931: 5931) hide_daemon: Permissive detected, hide the state

I( 5931: 5931) hide_utils: Re-linking /sbin

I( 2627: 2664) proc_monitor: com.google.android.gms.unstable (PID=8113 ns=mnt:[4026534430])

I( 8118: 8118) hide_daemon: Permissive detected, hide the state

I( 2627: 2664) proc_monitor: com.google.android.gms.unstable (PID=9884 ns=mnt:[4026534439])

I( 9889: 9889) hide_daemon: Permissive detected, hide the state
[Magisk] RespectThis:
Upgraded to v14.0 and so far I haven't run into any *major* issues. The modules I've installed have been done through TWRP and not the app, but no issues there. However I have pinned down one source for root disappearing. If I "close" Magisk Manager via the "Application Manager" on my Galaxy S6 it disappears every time. A reboot resolves it.

Tried searching to see if anyone had mentioned this but I didn't see anything. If more info is needed just LMK.
[Magisk] L30Bola:
XT1097 not working latest version (14.0)

Just updated to the latest version. I'm using the latest Stock Android for the XT1097, which is 6.0 - MPES24.49-18-7.

I was using v13.3 fine. Tried updating through the Magisk Manager, recovery (TWRP 3.1.1-0) and a clean install through recovery. None of them worked.

The device simply stays on the boot logo screen forever. Going back to v13.3 works.

So I went back to v13.3 to keep using Magisk. I'm attaching the logs to see if they can help. Any more debugging needed, just ask. I'll try to provide ASAP and if I have any doubt on how to proceed to help, I'll ask :)
[Magisk] reversegear:
@Didgeridoohan please help me on this

I have installed modules but not showing in modules list :(

Magisksu works fine

Device : Le1s

ROM : RR 5.8.3

Android version : 7.1.3

Edit : installing modules via Magisk gives this error

modules list always shows empty though i have modules installed via recovery

Magisk is installed correctly

let me know any particular logs are required
[Magisk] Didgeridoohan:
No, it doesn't.

No, you shouldn't have to. There are changes that might require you to clear data for the Manager though.

Samsung devices are quirky. The normal installation instructions are in the release thread. If you're device requires a special installation process you're probably better off checking in your device's forum.

What modules? And the entire Magisk log is more useful (attach the file, don't post the output directly).

You don't need ADB anymore (that was for the beta version). Generate the patched image with the Manager and then use fastboot.

fastboot flash boot patched_boot.img

You're device briefly didn't have a connection to the server... That's why you got the vnull thingy. Hm... I'll file that under bugs.

I don't think you'll be able to use the on-device patcher for now.

No. The permissive part shouldn't have anything to do with it. You could try by changing your device's SELinux to enforcing.

That's been noted from time to time. On some devices you'll get this if you clear the Manager from memory.

Looks like you have Xposed installed. Try removing it...

There are issues with mounting the system mirror. I'll file it under bug reports.

Edit: Does it work on v13.3?
[Magisk] reversegear:
Yes. only the modules with "automount" = false was working.

system mounting error was seen in 13.3 also.
[Magisk] Didgeridoohan:
Now that the Greenify4Magisk module is update to the current template, could you do me a favor?

Uninstall the module and see if it works installing it from the Manager now.
[Magisk] t0n4:
Running fine Magisk 14.0
[Magisk] Frankyfunkz:
Removed from modules by trash bin icon in magisk manager with reboot.

Downloaded and installed with magisk manager, no message about update.

All good boss, thanks for the help!
[Magisk] Aftab_khatri:
I have htc 10 Android 7.0 magisk 14 unable to boot phone. Back to 13.3 and everything normal, stock sense rom and no xposed
[Magisk] an0therus3r:
Installing and updating Magisk plus Manager went smooth on my OP5 but installing modules gives a Unable to extract error, any ideas?
[Magisk] Flavourized:
Device: OnePlus 5 A5000 (8GB + 128GB)

Magisk: v14

MagiskManager: v5.3.0

ROM: OxygenOS 4.5.10

Issue: I just did a *complete* wipe of my phone, OS and all. Flashed the stock OOS 4.5.10 onto the device and setup like normal. Rooted and installed magisk properly with TWRP 3.1.1.1-1 (Whatever the latest TWRP is). Whenever i try to install a Magisk module through MagiskManager, I get "Process Error". Here is the log from Magisk manager

What can i do to fix this? If there is no fix, is there another way i can install modules?
[Magisk] bhiga:
Okay, now I've really done it, haha.

Upgraded from Magisk 13.3 to 14.0 on Samsung S5 (T-Mobile), went fine.

Decided to try the Hide Magisk Manager function.

Seemed to have worked, got the Unhide Magisk Manager app.

Tried to restore Magisk Manager by running Unhide Magisk Manager. It didn't seem to do anything.

Rebooted, tried again, same.

Reinstalled Magisk from TWRP, same, no Magisk Manager, only Unhide Magisk Manager.

Uninstalled Magisk using latest uninstall zip, then reinstalled, still couldn't get Magisk Manager back, only stuck with Unhide Magisk Manager.

Then, I made it infinitely worse by uninstalling the Unhide Magisk Manager app, which uninstalled fine.

But now I have no Magisk Manager and root apps that previously worked hang on requesting root.

When I try to reinstall Magisk Manager via the APK, the system asks me about upgrading the existing app, so it's still sort of there, but I can't figure out how to either clear it out completely or get the Unhide Magisk Manager app back.

Reinstalling Magisk via TWRP gets me neither Magisk Manager nor Unhide Magisk Manager.

I think I've painted myself into a corner.
[Magisk] caliban_freak:
Get an error whiln try to install v14 on galaxy s8+

Gesendet von meinem SM-G955F mit Tapatalk
[Magisk] DodoGTA:
Restore boot image without SuperSU or go away
[Magisk] exadeci:
I love magisk but this last update got my phone in bootloop, I flashed the uninstaller it was still bootlooping and TWRP was now asking me for a password (never had one set) so I had to format data and even then my phone wasn't booting, I had to re-flash everything from 0 :(
[Magisk] BorrowedTime:
Clean install on Magma NX UX10. Installation goes fine but whatever module I chose I get process error. Anyone has any help?
[Magisk] ZidanBlaster:
Is anybody got an error when installing magisk modules on magisk 14.0
[Magisk] OSheden:
Since I upgraded to the latest versions of Magisk & Magisk Manager, my phone is slow (OnePlus 3T - 7.1.2). Wiping both cache partitions didn't help.

Is there a fix besides a clean flash of my custom rom?
[Magisk] civato:
Samsung S7 edge Stock TW 7.0

Magisk 13.3 SafetyNet Pass

Magisk 14.0 SafetyNet Fail

Same rom just other version of Magisk.
[Magisk] dimm0k:
as requested, attached are all the logs I could get for this. I even switched to the beta to get the debug log to see if that helps. lastly, I've also attached one of my basic modules I created that causes this.
[Magisk] Didgeridoohan:
To anyone experiencing bootloops: take a look at your modules (in recovery, flash Magisk Mount first).

If the system placeholder file hasn't been removed from the zip and you're manually installing the module this may cause a bootloop. Just delete the placeholder file from /magisk/<module_id>/system and you should be good to go.

Hopefully this can fix the issue for some...

---------- Post added at 14:08 ---------- Previous post was at 14:04 ----------

See my message above.
[Magisk] Aldideos:
Hi, i'm trying to install Magisk via the new installation method but I have a problem... When I select the boot.img it does nothing... I checked in MagiskManager folder and there is not both Magisk zip and the patched boot.img... I allowed the storage permission to Magisk manager... I don't know how to fix...
[Magisk] Viqta_:
Force close when I click search

Magisk manager force closes when I try to press search on the download page. I have the log of me reproducing the issue. I hope you will see it before it expires https://pastebin.com/6WcQe2SJ
[Magisk] krokodildo:
This solved bootloop issues on my Oneplus 3t (stock OOS) after updating to v14.0. Thanks!
[Magisk] lahceneamine:
Try to use TWRP file manager.

Naviguate to /data/app/ and delete the folder named "com.topjohnwu.magisk" (it maybe also "com.topjohnwu.magisk-2")

Then install Magisk Manager again, it should install the apk but I don't know if it will fix your issue.
[Magisk] Didgeridoohan:
If the above suggestion doesn't work, you could try running pm unhide through adb (I'm unsure if this is the proper syntax, you might want to Google it):

adb shell pm unhide com.topjohnwu.magisk
[Magisk] eng3:
On a Sony Xperia Z5 Compact with Lineage OS 14.1

It works fine with Magisk 13.3.

With 13.6 and 14.0, it hangs at the white Sony screen, does not get to the boot screen.

If I disable xposed, all the versions of Magisk work

I can get to TWRP and flash 13.3 back which fixes it.

Since it gets stuck before android boots, I can't get the log file
[Magisk] soder:
I have a very strange problem. First, my problem with Magisk 14 on OP3T was solved with the place holder being removed.

But, I got another problem with an "old' module, the appsystemizer.

When I try to remove it, by uninstallation, or like now when mounted in recovery, after boot up most of my apps are gone from my app drawer. Both the stock one and Google Pixel Launcher.

I can start the apps from the shortcuts I got, but in the drawer all but 5 apps are gone.

I don't know how to fix this. I don't want to have that module installed any longer (I prefer to manually add files to another module that has stuff added to some root folders).

I hope someone can help me with this.

/Söder
[Magisk] SavageDamage:
I have heard that Magisk has a new ADB installation method. Does that mean I can apply it to stock without unlocking bootloader and flashing a custom recovery?
[Magisk] KaMyKaSii:
With a file manager, check for the existence of the "MagiskManager" folder in internal memory. Probably it does not exist. Then create it manually. Force close Magisk Manager and clear cache. Open it again and you can now download the modules
[Magisk] DallasBelt:
Same here, although modules are working fine. The delete button (thrash can) doesn't work though.
[Magisk] Frankyfunkz:
Didgeridoohan has already helped me fix it.

Remove the Module folders in /Magiskmanager/

then restart the magisk manager app.

Download your modules' zip files from the download section in magisk manager but dont install. Reboot into recovery and install them from there. Assuming you have a recovery tool like TWRP set up.
[Magisk] KaMyKaSii:
No. You still need to unlock the bootloader (in order to install patched boot.img) or use some other method that your device/manufacturer offers
[Magisk] DallasBelt:
Thanks! But now I can't download modules from Magisk. Got "Process error". Im going to reflash Magisk to see if it helps.
[Magisk] Frankyfunkz:
This should help you fix it, seems to be for the same issue.
[Magisk] DallasBelt:
Worked perfectly! Thanks a lot (:

---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------

Intall the module from Magisk, then reboot.