yashsingh1/xdaforums huggingface dataset:
[Magisk] Timmmmaaahh!:
Then apply the same solution :D
[Magisk] neokragu:
I am not the fan of the stock MI ROMs. I feel its better to get in custom ROMs.
[Magisk] Artim_96:
Then choose. Either custom ROM or banking
[Magisk] neokragu:
Already chosen, go with custom ROMs. So I need to compromise with banking app.
[Magisk] robbayani:
succesfully install Magisk 14 on Nitrogen OS 7.1.2..

but when install any module via Magisk Manager it said FAILED!!

trying download only also failed..

is magisk repo server error??
[Magisk] gugugrp:
I had the same problem! Uninstall Magisk with apk already installed, clean Cache/Dalvik, and then install it again.

Enviado de meu Moto MAXX usando Tapatalk
[Magisk] demonoidmaster:
Make a MagiskManager folder in /sdcard
[Magisk] robbayani:
okayy.. i'll try tomorrow..

when Clean install + Magisk 13(all works well) its automatically making MagiskManager folder..

now also Clean install + Magisk 14(install module error) should i making folder manually??
[Magisk] Didgeridoohan:
If the folder isn't there, yes. Also make sure that the Manager has got storage permission.
[Magisk] Myp3a:
OnePlus 3T, HydrogenOS, Android 8.0, Magisk 14. Stuck on splashscreen with Magisk. "Your bootloader is unlocked" warning, "dm-verity not in enforcing mode" warning - and stuck on bootlogo. No logs, /data not mounted (And encrypted). Magisk folder in /data exists, so it is installed properly.

My boot.img here - https://drive.google.com/file/d/0B0cvu4GPKhyVUk9vb3M4Y0t2RVk/view?usp=drivesdk

Btw, SuperSU works fine here.
[Magisk] demonoidmaster:
Didn't i just tell you to make the folder ?
[Magisk] Alc@h0l1k81n05avr:
Hey again. Big thank you for the advice, I've managed to do a clean install of my Huawei P9 Lite VNS-L31 Nougat Rom and can now root again flawlessly :D that being said i've run into a strange problem with the latest magisk. I installed version 14.0 and everything was working out fine like it usually does, or so i thought. Magisk Manager took a little longer to search for updates than it usually did and strangely ended with something like 'cannot check for updates, no internet?' I ignored it thinking it wasn't really big but I then went into the downloads section to get all my modules and the screen was blank and just kept loading with the refresh icon and when i tried to search for a modules magisk manager would crash and quit; I tried installing earlier versions of magisk and magisk manager to see if that would sort out the problem, but nothing happened. I didn't get problems like these when I used magisk a few months ago so I'm not really sure what's causing the problem, has anyone else here gone the same thing and if so are there any solutions to this because I just want to install viper4android with no problems.
[Magisk] xuthus.wong:
Dear developer, Flashing Magisk-uninstaller-20170906.zip can't restore the original stock boot image dump in Recovery. And I get the message "Boot image backup unavailable".
[Magisk] Didgeridoohan:
The go-to solution when something is off with the Manager is to clear data for it. Have you tried that? Also, you don't happen to have any so/service that restricts internet access?

There's a bug in v14.0 where the Magisk installer won't properly create the backup. It's been fixed for the next release.
[Magisk] freemannhp:
What happened to my phone is if you use the method of fastboot patched boot.img, stock boot will be backed up sucessfully. If you install magisk via twrp, it fails to back up stock boot.
[Magisk] mrceli:
just updated from 13.3 to 14.0 with direct install. runs flawlessly. thanks.
[Magisk] karunia72:
Update from magiks manager?
[Magisk] liviumustata@yahoo.com:
thanks - no more erorr!
[Magisk] DodoGTA:
"erorr" :laugh:
[Magisk] Raihan14z:
When I download module on magisk manager .. Magisk say

"procces error " so i cant download or install it ?

Can you fix this bro ??
[Magisk] Captain_Throwback:
Can you search bro ??
[Magisk] Raihan14z:
Thansk broo , i already fix it use this method
[Magisk] Timmmmaaahh!:
I've encountered something similar with the universal SafetyNet fix. You can also flash modules in recovery, worked fine for me.
[Magisk] t0n4:
Create MagiskManager folder in the sdcard
[Magisk] Raihan14z:
I've found a way

---------- Post added at 03:06 PM ---------- Previous post was at 02:46 PM ----------

Sorry out of topic

how to set the minimum value of brightness through the system?
[Magisk] gudenau:
Could anyone help me? I can't manage to install TWRP on my Pixel XL which means I can't flash the 14.1 beta.
[Magisk] koraymers:
You will update Xposed 87.3 by [MENTION=4470081]topjohnwu[/MENTION] right? Cuz I'm stuck on splash screen after updated magisk ver 14.1 from 1400

RR OS 7.1.2 Sirius
[Magisk] immi803:
Xposed v87.3 breaks my wifi, device overplus 3t, kernel dorimanx, disabling module make it work again

Same experienced with 1400 and 1410 magisk

Else everything's fine

Just reporting
[Magisk] ]grimm[:
Pixel C boot image repack error

14.2 continues not to install on the Pixel C. I believe that the last version to properly install was 13.6. 14.12(as with previous versions) can be installed in a facile sense by using the boot patch script from 13.6 and adding in the updated magisk binaries.
[Magisk] lahceneamine:
Try to boot into recovery & reflash v14.0
[Magisk] TheC92:
Good?
[Magisk] Dentora:
Device: Galaxy 7 (930W8)

7.0 Stock rom with SuperStock kernel.

TWRP 3.1.1-0

The latest build works mostly fine. It passes safety net and provides root fine didn't seem to go away. unless I try to install a module the iYTBP module in this case. it installs, reboots and then nothing seems to happen on restart and the module doesn't show in the manger, then safety net starts failing.
[Magisk] DenyDarko:
This beta attempts to fix boot patching issues.

Yours is fixed too so it's a success.

Modules is another thing

PS: Guys I hope you restored stock boot (used the uninstaller) before installing the test build before reporting success, right?

I'm asking because you don't provide logs so the installation process can't be seen.
[Magisk] shadavis08:
Maybe not but when I installed on my v20 it caused a slow boot loop. So I had to reflash my phone to get rid of it.
[Magisk] Dentora:
Yeah I used the latest uninstaller and uninstalled the old manager before updating anything.
[Magisk] DodoGTA:
Device: Samsung Galaxy Trend Plus (GT-S7580)

ROM: Unofficial LOS 14.1 ROM with May 2017 security patches (dated 20160603)

Kernel: The one that came with the ROM

Recovery: TWRP 3.0.2-0

It works well so far (I did an upgrade from Magisk v13.0 0b4baad build)

Screenshot:
[Magisk] DenyDarko:
Upgrading from previous was working for most people with the link error.

The issue appears when zip tries to patch a stock boot image directly from v13.
[Magisk] fndpena:
Do I need to flash the latest version if I don't have boot patching issues?
[Magisk] erayrafet:
Hi! With the latest version of Magisk i was able to pass SafetyNet checks. The root access was getting lost in V12 that doesn't happen in V13 but previous V13 builds weren't able to pass SafetyNet so big THANKS!

Device: Huawei P8

Software: Android 6.0 EMUI 4.0.3, June Security patch.

Recovery: TWRP 3.1.1
[Magisk] Jerome Shaw-PRC:
Viper4Android module is not supported, it doesn't work at v13, probably I should ask the developer of v4a?
[Magisk] vitekrus777:
[MENTION=4470081]topjohnwu[/MENTION] thank you so much! Version 2 is installed and working. The truth does not pass the profile check.

Log and screenshot attached.
[Magisk] Artim_96:
It works, at least for me.

On EmotionOS/LOS 14
[Magisk] KenjiHannya:
Work im my Kenzo

Omni ROM 7.1.2

Magisk-v13.0(0b4baad).zip

Tnx guys ;D
[Magisk] djb77:
The zip works fine on Galaxy S7 G930F now.

Safetynet works fine, so does MagiskSU :)
[Magisk] Timmmmaaahh!:
You don't need to do anything but you are welcome to to do so if you want to aid development. The focus here is on bug reporting, not about what's currently the best option for users. You could say we're shaping the best option of the future for users.

On that note, latest (1777d9f) is now fully functional on OnePlus One RR N 7.1.2 here. SafetyNet passes nicely, modules install perfectly, Magisk hide is.. well, hiding. Cool beans! :cool:

♫ keep on flashing ♫
[Magisk] yochananmarqos:
When a module causes your device not to boot, you can flash the Mount Magisk ZIP (attached here) in TWRP to mount /magisk. Then use the TWRP file manager to delete the offending module's folder. Remember, Magisk does not touch your system partition.
[Magisk] Windforce0511:
After flashing magisk module, phone stuck at Samsung Galaxy logo. After that I must restore stock boot image and flash v13 again, then phone booted up normally but no moudles. (Galaxy S6 Nougat)
[Magisk] wrongway213:
Device: Nexus 6

1777df9_v2 flashed normally, no issues

Properly rooted

Systemless hosts working normally

Modules working normally

Passing SafetyNet

:good:
[Magisk] Deic:
All is work as intended, it could be a problem external to Magisk. Try this: create a file called "system.prop" in /magisk/.core/props and write this inside

ro.build.fingerprint=Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ro.bootimage.build.fingerprint=Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ro.build.type=user
ro.build.tags=release-keys
ro.build.selinux=0
selinux.reload_policy=1

And reboot.
[Magisk] demonoidmaster:
Theres an uninstaller for that yknow
[Magisk] freemannhp:
You don't need twrp to flash magisk, check install instruction on https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] lululala:
upgraded from 14.0 to 14.1. looks like 14.1 broke Arise with magisk compatibility module (https://xdaforums.com/android/softw...-research-t3379709/post71569390#post71569390) . reverted to 14.0 and it works again.
[Magisk] gudenau:
When I tried to use ADB it didn't install though.
[Magisk] JERW28:
[MENTION=4470081]topjohnwu[/MENTION]- same problem on my device. If I delete your Xposed 25 87.3, the phone starts normally, no problem. Logs attached. Thank you

Version: Magisk 14.1(1410)

Architecture: ARM
[Magisk] 1112ee:
Substratum isn't working for me on 14.1
[Magisk] jeonggeek:
Boot doesnt work after update to 14.1...
[Magisk] yochananmarqos:
This is not a TWRP support thread.

You will provide logs, right?

Logs or it didn't happen.

This isn't the ARISE thread.

This isn't the Substratum thread.

Did anyone perform any troubleshooting steps before posting?

This is the beta thread. Re-read the OP. Logs or it didn't happen.
[Magisk] JakeDHS07:
Well I tried this on my Pixel XL. Installs fine and works with most apps. Unlike SuperSU it doesn't ruin TWRP reboot to recovery. However it does crash Substratum which apparently doesn't work with Magisk. Currently I'd rather have my themes then on the go recovery. So back to SuperSU I go for now.
[Magisk] Falitheman:
Could you give me instructions on how to install this on the pixel xl? I'm on a custom rom based on 7.1.2.
[Magisk] JakeDHS07:
Pretty simple really. Install the current Magisk manager 5.3.5 either from the op or xda labs beta channel (this is what I used) once that's done open Magisk and enable the beta updates in settings which will point you to 14.1 when you choose to install it that will download the zip. Fastboot boot TWRP if you don't have it already or reboot to recovery if you do and flash 14.1 zip.
[Magisk] Paschfire:
Device? Current setup? Logs?... ARISE, compatibly module and Magisk v14.1(1410) beta working just fine here.

Also.. for ARISE Support pls forward your questions here within the ARISE XDA thread. >https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

(My device information within signature below, or profile page.)
[Magisk] Denkai:
I know logs or it didn't happen, but I can't boot with 14.1 to make a log, system goes straight to bootloader. Reflashing 14.0 didn't help, had to restore image. Flashed via app and TWRP, nothing worked.

OnePlus 5

OxygenOS 4.5.10.
[Magisk] MortimerR:
Well that was a great waste of an entire night.

Updated Magisk to the newest version (using the updater in the manager) and on reboot, system would not boot up correctly. Ended up having to adb sideload (first had to set up adb) the uninstaller package because every .zip is busted. Anyone have a version that actually works?
[Magisk] Paschfire:
Device? Setup information? Logs?

No one can help you if you don't provide the necessary info.
[Magisk] Pkt_Lnt:
adb logcat will get a log from turned off thru start all the way to full or partial boot.

Devs use it as the *only* way to find out *why* a ROM will not boot fully.

Here is a logcat tutorial. :good:
[Magisk] m.atif:
Failed to boot on Mi A1 (Android one)

Mi A1 have A/B partition like pixel.

I have tried patching boot.img and boot & flash the patched boot.img, doesn't work

CF auto root patched boot.img roots the phone but destroys OTA (I guess) that's why I was trying magisk . Magisk manager patched the boot successfully but if I boot the patched boot.img from fastboot it does not root the phone also flashing the patched boot to current boot partition (_b) gives boot loop.

Tried to get logs but got no device detection in adb so empty file.
[Magisk] osrox:
[MENTION=4470081]topjohnwu[/MENTION] Really happy to see support for A/B partition added in Magisk 14.1

Will this work on Mi A1, similar to Google Pixel ?
[Magisk] Pkt_Lnt:
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^

*one* post above yours! :D
[Magisk] TheColin21:
bootloop

14.1 bootloops on my OnePlus 5 running xXx No Limits 3.5
[Magisk] Ex-Hunter:
[MENTION=7470500]m.atif[/MENTION] [MENTION=6255216]osrox[/MENTION]

Have you installed the September update?
[Magisk] m.atif:
No , I was rooted by CF auto root, so I didn't tried
[Magisk] Denkai:
Yea, I don't even get to the Boot screen let alone get ADB up and running. it's not boot looping, it's not booting at all, like the boot.img is damaged. but to entertain, I pulled two magisk logs from the cache via recovery. doubt it'll have anything from the failed boot, but maybe.
[Magisk] obol2:
same, did you managed to fix it? I want to uninstall magisk and try to boot again.
[Magisk] denistina:):
I dirty flashed it on my kenzo NOS O over 14.0, works fine I guess :) not sure if i still need magisk v14 safetynet hotfix v2 beta5.

Thank you
[Magisk] TheColin21:
I just dirty flashed the ROM including magisk 14.0
[Magisk] obol2:
Ok i fix it that by uninstalling magisk, then install 14.0 :) this is a faster way i think
[Magisk] veez21:
[MENTION=4470081]topjohnwu[/MENTION] , would you consider making a documentation on A/B partitioning for module developers?
[Magisk] BajinganTengik:
I experienced this before, but it solved by installing busybox by YDS.
[Magisk] DenyDarko:
Just installed the 14.1

It's running just fine on LG G5 H850. No bootloops. Everything's (including modules and safetynet) working smoothly.

I guess it's something with specific devices.
[Magisk] dugi9991:
Using it on OP3 with DU without any problems, flashed, booted, it just works ;)
[Magisk] mystique47:
14.1 with oneplus 5 + aicp and flash kernel = no audio play and record -> causes crashes and reboots. No audio modules.14.0 works good
[Magisk] Rom:
You miss logs files.
[Magisk] Artim_96:
With v14.1 my phone refuses to boot. It's stuck on that Samsung splash screen (or it takes much longer to overcome it, I don't know). I tried both installing through Magisk manager (updated it first) and through TWRP

Galaxy note 4 with RR 5.8.4, based on N with August patch
[Magisk] themasv:
Installed v14.1 on my Oneplus5 running stock oxygen os and got bootloop, did dirty flash v14 and it did boot.
[Magisk] smartpr1v4t3:
Hey guys,

i had the problem with 14.0 on my OnePlus 3t that the Phone didnt boot, as i was told its because of the old versions of the magisk modules.

There is a file that needs to be deletet.

Is this problem still persistent in 14.1 and if yes can anybody tell me what file/folder this was?

Thanks
[Magisk] ofirmz:
this works for me., thank you., save me :)
[Magisk] smartpr1v4t3:
Found out what file^^

Was the DCI-P3 Module for OnePlus had the placeholder file, after deleting phone bootet with 14.1

/magisk/<module name>/system
[Magisk] droopyar:
Excellent news for the update. Please include busybox inside during the installation
[Magisk] denyo81:
14.1 is stuck in the boot.

Oneplus X
[Magisk] Denkai:
I did a complete uninstall with no modules, still stuck at bootloader. OP5 4.5.10.
[Magisk] smartpr1v4t3:
I use a OP3t and others reportet OP5 has boot problem.
[Magisk] Denkai:
Yea, I'm one of the reports. Just posting to keep trackif what has and hasn't worked.
[Magisk] xthek1ng:
Will this work if you already have Magisk installed on the device? I have 13.3 b4 by Goodwin running on my PXL right now. Can I just update through the app?
[Magisk] wanam:
[MENTION=4470081]topjohnwu[/MENTION] thanks for the pixel update.

Just wanted to report a possible bug with your busybox binaries, "unzip" does not seem to work on "/data/local/tmp", it works with supersu.

Running the latest Pixel stock 7.1.2 Rom.
[Magisk] gloeyisk:
Thanks for your Best work. Loved it!
[Magisk] Psy0ch:
Bootloop on OP3 with Magisk 14.1, trying to dirtyflash V14 rn

//Edit: Nope, wont help. It asks for my sim card code and immediately reboots
[Magisk] topjohnwu:
2017.9.29 Magisk 14.2

A critical bug slipped through which could break 99% of modules. The issue was now fixed, and you should be able to use your favorite modules normally now!

Sorry for the inconvenience!
[Magisk] Nevermindthelabel:
Awesome, just flashed 14.2 on my OP3 OB 24 and all works great.
[Magisk] Base2:
Magisk with File Based Encryption?

The change log for Magisk 14.1 indicates that it has support for file based encryption. From the release information this was tailored principally for the Pixels, but. Has anyone successfully installed Magisk with Android Oreo 8.0.0 encrypted using file based encryption? I tried it on a Nexus 6P with opr6.170623.019 and Magisk-14.1 and it never went beyond never ending boot animation. (and no, I didn't try this on top of SuperSU, I started from an unrooted stock bootable image.)

Edit: Tried again with 14.2. No change at all.

Back to SuperSU again for now I guess.
[Magisk] andynx1:
14.2 installed here, all good. Moto G 5+, LOS15.
[Magisk] T.A.R.D.I.S.:
Works fine on S7 edge on SuperMan rom 2.6 :good:
[Magisk] Istvan_86:
I have the same issue as you. How can I attach a proper log?

Thanks.
[Magisk] dugi9991:
Can confirm, v14.2 works flawlessly!
[Magisk] lordregnis:
Ive been on 13.2 with also a file i downloaded somewhere on here that let me pass safetynet so i could play pokemon go. Stopped working for me today, was safetynet updated? Any help getting this working again would be appreciate, thanks.
[Magisk] surenther.ss:
I am using Pixel XL with custom rom 7.1.2. I have installed latest 14.2 Magisk . It was working and safety net also getting passed. But when i tried to restore an app through Titanium backup. It's getting struck at restoring. Googling about this came back with issues in binary. Is any one facing this problem? or is it any way to update binary in Magisk? . Tried installing Busy box to check about binary. That's also came back with corrupted binary message.
[Magisk] toastyp:
Latest magisk 14.2 will not flash for lgv20. Error 1 when flashing in TWRP. Stops at unpacking boot images and fails. Running stock 7.0 rom with stock boot image.
[Magisk] nathanchance:
recovery.log?
[Magisk] toastyp:
Sorry phone couldn't upload it for some reason. Had to get to my computer -here it is
[Magisk] Istvan_86:
Hello,

Magisk v14.2 fails with error: 1 in Pixel C. Here is the log.

Latest version that I can use was v13.6 I also upload a log of the installation of v13.6.

Also I must add that is working flawlessly on my OP 3T.

Hope you can fix it!!!!

Thanks in advance.
[Magisk] krekis:
working perfectly on my Kate (RR 5.8.5).

thanks dev... :D
[Magisk] Mezabaru:
No issues on Batman rom S7 flat!
[Magisk] jeonggeek:
Boot is ok after 14.2. thanks for ur hard work
[Magisk] mystique47:
14.2 fixes all. Thank you
[Magisk] HeaDekBatHblu:
After installation on Nextbit Robin with ParanoidAndroid 7.3.0 - no sound (in all speakers) and bootanimation, downgrade to 14.0 - all ok. Fix it, please.
[Magisk] Captain_Throwback:
14.2? Or the broken 14.1?

Also, no logs...
[Magisk] psychoela:
Flashing with twrp 14.2 over 14 still bootloop,rom RR final,flash successful without error,ss is module already install.thanks
[Magisk] Brouss:
Just updated apk to 5.3.5, then flashed 14.2 thru magisk. All worked perfectly.

OP5

official RR (sept5)
[Magisk] demonoidmaster:
L

O

G

S
[Magisk] manos78:
Hi,

I have one suggestion for the MagiskManager: Add the option for "Reboot" when changing the module status (enabled/disabled). As the Power Menu doesn't has the Reboot option, then will be interesting to have the option for reboot from the App (as Xposed Manager does when install a new module).

You agree?
[Magisk] februarysn0w:
Here with oneplus 3T /Tugapower N36 no issue on boot. on 14.1 boot looped.

Thank you for your update.
[Magisk] lucasdeeiroz:
Hello, i have a Lenovo Vibe K5 Plus and it was working fine on Magisk 14.0. Since 14.1 update, tho, I have to install magisk every reboot and the bootlogo freezes for about 1min. I can live with those issues, of course, but they are super annoying. Thanks anyway, your work is impressive.
[Magisk] Captain_Throwback:
Did you update to 14.2?
[Magisk] lucasdeeiroz:
Yes, same issues.
[Magisk] s0917:
I am installing via MagiskManager on my Xiaomi Mi A1 since there is no official custom recovery yet like TWRP and etc.

After I patched my boot.img and flash it I got stuck in bootloop.
[Magisk] lucasdeeiroz:
I just rebooted my phone to pick up the logs (I don't know if it was needed, but I did anyway), and the phone booted normally... that was the first time this happened since 14.1 update. Weird.

If the bug appears again, I'll post the logs. Thanks.
[Magisk] psychoela:
this my logs ,thanks:D
[Magisk] Captain_Throwback:
Logs.
[Magisk] gaww:
I downloaded 14.2 zip and installed the embedded Magisk App 5.3.5. When I open it, it still only shows latest version as 14.0, so no option to update?

I can only update when on duelboot apps, and prefer to do it when possible, as it usually has no issues.
[Magisk] Didgeridoohan:
Have you changed to the beta channel in the Manager settings?
[Magisk] DodoGTA:
Beautify mode for your profile picture? :laugh:

---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------

l g

o o t

g r f

s o
[Magisk] wiggmpk:
Pixel XL here, running stock Android Oreo (Sept). Upgraded from my build of Magisk 14.0 (thank you for your work topjohnwu and making the source available) everything was working pretty well. topjohnwu came back from vaca and put out the 14.1 beta, updated to his version and everything was working pretty well. I just updated to 14.2 from recovery and Magisk updated but it didn't update Magisk Manager, still running 5.3.0.

I tried uninstalling Magisk completely (with the flashable uninstaller) and installing Magisk 14.2 from recovery. Everything looks like it completes fine, no errors, but rebooting yields no Magisk Manager installed and, of course, no root access.

I tried reinstalling 14.0 (my compiled version), rebooting to recovery, flashing v14.2 over my build and upgrading Magisk Manager from within the app, allowed the permission to install from "unknown source" and it just fails, says "App not installed"

Any thoughts?
[Magisk] psychoela:
Please help [MENTION=6429309]DodoGTA[/MENTION]

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post73976625