yashsingh1/xdaforums huggingface dataset:
[Magisk] Rhymcuk:
Honor 7

Hello, I rooted my device with "Magisk". Then my device requested SIM NCK code. How can I resolve it? ( I used google translation.)
[Magisk] czupakabra:
Whats is wrong with safety net on android 7.0 on my p9 lite? One day everything is ok, safety net is OK, then i instaled other stuff like elitekernel reborn and others mods, and next day there is false! When i was on nadroid 6.0 safety was stable always. it starts to pissed me off!!!
[Magisk] jenslody:
Is internet working ?

Can MagiskManager access internet (firewall) ?

Which update channel is selected ?
[Magisk] hemantv:
That's something I'm confused about too. If I check my /system/build.prop file, there is no entry for qemu.hw.mainkeys. But if I execute getprop command it is included in the output list with value as 1. :confused:

I can share my build.prop file if there is a need.
[Magisk] jenslody:
It looks like the bootimage patcher can not detect the format of your bootimage.

Can you upload it somewhere, so it can be checked ?
[Magisk] jhill110:
I'm on 15.3 with MM 5.5.5. I just looked in modules and a module called MHD helper is installed. I didn't install it. What the heck is it?
[Magisk] 4ndr0x:
Internet is working, selected update channel is stable.

I've just tried it again and now it worked fine and prompted me to upgrade. Was probably a temporary server problem.
[Magisk] skymera:
Bumping this . Anyone?
[Magisk] PokemonTotalWar:
I just checked, it appears not to. Can I simply create the folder with the right permissions, or will that cause issues? Also, isn't there usually an sbin in the system folder? I seem to only have bin. Thank you!
[Magisk] skribb:
Trying to flash with TWRP on my Z2 Play.

I left the flashing on, and after 8 hours it was still at "found boot image" so I give up for now. I rebooted the phone. Not bricked fortunately.

Any ideas?
[Magisk] martyfender:
On my devices, sbin is at the root level, not in the system dir.

---------- Post added at 02:49 PM ---------- Previous post was at 02:27 PM ----------

This is strange, I toggled to deny storage permissions to the Magisk Manager and the Magisk Hide toggle remains enabled now, even after a reboot. It is does appear that enabling it in the first place is what triggered it to work though, because everything else I tried: delete data and cache, uninstall Magisk Manager and reinstall and boot to TWRP and delete cache and dalvik cache did not have any effect. The only thing I did not try was to flash the Magisk uninstaller.zip in TWRP and reflash the Magisk 15.3.zip

I still may try the beta, but I enabled the beta channel in the settings and it shows that I am up to date: v15.3 stable and Magisk Manager v5.5.5. Do I need to click install anyway for it to download the current beta and install over the current stable or would it be advisable to download and flash again through TWRP, over the current stable. Or would it be better to flash the Magisk uninstaller.zip again, first?

I am tempted to leave it as is though, since it is working now.

By the way, does the debugging code in the beta add any additional overhead, or is it not noticed on most devices? I do frequently test beta apps from other developers here on xda, often providing feedback.

Thanks
[Magisk] EricHegnes:
Magisk crashes when not able to access the cache for logging purposes?

SOLVED: by formatting /cache to EXT4 rather than F2FS.
[Magisk] n.p.:
Yes, the basics (root) are working (but not both SafetyNet tests) after reflashing several times (don't know why it takes so many attempts).

Since using MagiskManager is the "highly recommended" way to upgrade, it would be nice if it worked. :)

I understand the log doesn't say much enlightening, but that is all that the upgrade attempt produced. :) Would be happy to try to debug future upgrade attempts.
[Magisk] Sagar Sharma01:
I installed magisk v15.3 but it doesn't installing any module except busybox ndk. And in /data/magisk there's nothing
[Magisk] martyfender:
I installed the beta 15.3 debug build, anyway, despite Magisk Hide working after enabling storage permissions. I have attached the debug log. Please let me know how it looks. I am new to Magisk and am liking it very much, so far, considering especially the current lack of development of SuperSu and even more importantly, the lack of the even a whisper from the new developers, that purchased SuperSU.
[Magisk] droidwarior:
Thanks for the systemless magisk but i m having

Force close error whenever i open magisk manager

Then it force stop (While the internet connection is on)

Magisk version 14.5

Magisk manager latest 5.5.5(91)

Here's the log

java.util.ConcurrentModificationException

at java.util.LinkedList$LinkIterator.remove(LinkedList.java:167)

at java.util.LinkedList.removeOneOccurrence(LinkedList.java:837)

at java.util.LinkedList.removeFirstOccurrenceImpl(LinkedList.java:830)

at java.util.LinkedList.remove(LinkedList.java:665)

at com.topjohnwu.magisk.asyncs.UpdateRepos.lambda$loadJSON$0$UpdateRepos(Unknown Source)

at com.topjohnwu.magisk.asyncs.UpdateRepos$$Lambda$0.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)

at java.lang.Thread.run(Thread.java:818)
[Magisk] Didgeridoohan:
I did some tests and setting props with system.prop works as expected.

I'm suspecting that there's something on your device already setting that prop to 1, sometime between Magisk loading the system.prop and running the service.sh script. Very wild guess, but that's the only thing that makes sense from your description. Using service.sh, like you have, is a perfectly valid way of setting the prop as well, so I guess that's what you'll need to use. :D

I assume you're using a custom ROM and don't care about official OTAs. In that case you should be fine editing /system and adding the folder. For simplicity and future updates, you could ask your ROM creator to add the folder though...

Check /data/adb/magisk instead (/data/magisk is just a symlink there, kept for some backwards compatibility).

If it's empty your Magisk installation is broken. Uninstall and try again.

From a quick look the log looks pretty good, as far as Magisk is concerned. There's a single error for the proc monitor, but after that it looks like it's working.
[Magisk] Gen5:
Can magisk be installed on a nexus 9 running 7.1.1 (october 2017 security update)? If so, how? If not, whats the latest security update/version of android that i can run that will allow me to install magisk? Ive tried flashing it in twrp, but i keep getting a failed install.
[Magisk] Didgeridoohan:
Got nothing to do with security updates.

If you want help you should at the minimum post the recovery log from the failed install.
[Magisk] Gen5:
I dont know how to post a recovery log. When i try to flash it in twrp, i get
[Magisk] Didgeridoohan:
Here you go:

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] Sagar Sharma01:
The folder isn't empty. Here's the Screenshot.
[Magisk] Didgeridoohan:
No, it's not empty. But on the other hand, it's not even there...

There's supposed to be a magisk folder under /data/adb (that's what I meant with /data/adb/magisk). Your installation is broken. Start over...

If you experience further troubles, make sure to provide relevant logs.
[Magisk] Sagar Sharma01:
Here's the boot img and installation/recovery log.
[Magisk] Sagar Sharma01:
How to uninstall it because magisk unstaller zip isn't detecting my boot img in custom recovery .
[Magisk] Didgeridoohan:
And nothing happens when pressing Uninstall in the Manager, or?

You could try just letting the Manager patch your boot image and flash that over your current setup.
[Magisk] Sagar Sharma01:
Thanks bro it worked.
[Magisk] DogGunn:
I've installed Magisk, and I have root access with my apps now, but despite pressing 'grant superuser access forever', it never seems to store that, and the app never shows up in Magsik Manager > Superuser. What am I doing wrong?

EDIT: There are sqlite errors in the log, however I've done multiple uninstalls and reinstalls of Magisk fully, using the zip provided.
[Magisk] Sizzlechest:
I just installed Chase Pay and it detects root. I upgraded to 15.1, but it still detects root.
[Magisk] mctiew:
Any chance of supporting this boot image ? Magisk says unable to unpack initramfs.

Boot image :-

https://drive.google.com/file/d/11uvwdJzUJH_Zu2Ll6Uq1XqXALeKnsOe1/view?usp=drivesdk
[Magisk] anthromg:
Update! So I completely uninstalled Magisk , wiped my cache and reinstalled Magisk and my WiFi returned for about 24 hours until my battery died again and my WiFi Mac address was reset to 02.00.00.00.00.00 , which I've noticed was a reoccurring issue. I tried wiping my cache again without uninstalling Magisk and my WiFi didn't return, so I've uninstalled Magisk 15.3 again and wiped my cache and haven't reinstalled Magisk and now my WiFi is working at the moment. [emoji849]

Note ; I might try flashing Magisk v14 again since I didn't have any WiFi issues prior to v15.
[Magisk] Shtiff1:
You should be on 15.3
[Magisk] Wolfcity:
Sorry for some kind of noobish question but I´m not very familiar with encrypted devices, the Moto G5+ is the first one I own.

I unlocked my bootloader and flashed official TWRP recovery. As stated in the rooting tutorial I was following I skipped the password check for decryption and flashed magisk, for the beginning v14 because it has been rockstable on my Titan and updating to 15.3 is always possible.

I knew that because of the f2fs bug magisk hide and modules aren´t working, no big problem for me at the moment. If it gets one I´ll flash a custom kernel.

Everything else is working as expected, Adaway (systemless hosts), Titanium, SD Maid etc.

But the data partition is still encrypted, so I can´t do a full nandroid backup because TWRP can´t mount data.

My main question is:

Is there any advantage (or disadvantage) to have the device encrypted or should it be decrypted? TWRP forces me to format data but as far as I know it will format it to ext4 by default. I can change it to f2fs but I´m not sure if it´s good that way.

I read in several threads that magisk will "handle" the decryption whatever that means.

So could someone tell me if I should decrypt the data partition (maybe just to be able to do full nandroids) and how or if it´s ok to let it encrypted.

I´m on 7.0 stock rom, build NPNS25.137-33-11.

Thx!
[Magisk] sumicool7:
I'm having the exact same issue :crying:

Although I don't see the SQLite errors in the logs. Can anyone help in this regards?

Thank you :)
[Magisk] Sizzlechest:
Yes, sorry. it's 15.3. I did enable hiding for the Chase Pay app, but it still detects root.
[Magisk] Shtiff1:
Also hide the Manager. Clear app data and cache. Reboot.
[Magisk] Sizzlechest:
What do you mean "hide the manager?" I cleared the data and cache. Still detects root.
[Magisk] jhill110:
In magisk settings.
[Magisk] Sizzlechest:
Hiding the manager did the trick
[Magisk] xiiihyou13:
my superuser wont stick and there is no superuser log. tried every magisk version since 14.x still the same problem.
[Magisk] Jiibus:
Disregard. I'm an idiot.
[Magisk] exalented:
Hello. Sort of new to Magisk, but so far my experience with it has been really good because I can pass safetynet! :)

I am here because of one main reason, but also because I want to figure out if I'm doing something wrong.

I want this > fingerprint-authentication-root-access , but I am currently on 5.3.5 with 14.2 MAGISKSU.

The only way I am able to get Magisk to work on my rom (Nemesis-Refined-n7 port for the Note 4 Exynos variants) is by using this UniversalSafteyNet Fix. I've tried installing modules without it and the modules aren't activated or even in the modulo list until I apply that fix. I've tried updating Magisk and Magisk Manager and I'm left with a reboot loop which just shows my boot loader over and over again (I had to re-flash my ROM to get it working again).

Is this something I need to look into?

Thanks.

EDIT: I forgot to add, during my tests with the newer Magisk versions I did have DualBootPatcher installed with the bootui. Perhaps this is causing issues?
[Magisk] Imdeepjee:
Worked fine on my Canadian S7 Edge (SM-G935W8).

In TWRP wiped my data and Flashed Magisk zip and samsung antiroot removal kit zip.

Thanks
[Magisk] mctiew:
Sorry still wondering why magisk refuse to unpack this boot image and gives error ?

I could use other tools to unpack the initramfs, it is just a normal cpio.gz format.
[Magisk] Didgeridoohan:
What's your device and ROM?
[Magisk] kosmatyj:
My apologises if was asked before. Still can`t install Magisk on Nokia 5. Patched boot not accepted by the bootloader. But Chineese guys have made SU installing correct with the boot`s sign preservation. So question is: when the Magisk will have ability to make the same? Regards.
[Magisk] Didgeridoohan:
Never ask for an ETA...

But, if there's any chance of Magisk working on that device you're going to have to provide some data. Info on what these other guys did, an installation log and a copy of the device's boot image is a start. None of that info guarantees that there'll be compatibility, but it's a start.

---------- Post added at 17:00 ---------- Previous post was at 16:48 ----------

If you're just looking for the fingerprint authentication for superuser requests, update the Manager only. That's just in the app...

Have you tried doing a clean install of the latest version? As in: first uninstalling Magisk completely and reinstalling? It's quite possible that the dual boot is causing issues. I know next to nothing about that though, so that's just a guess...

If you can't get things working, take a look in the troubleshooting guide, under "Bootloop". There are a few tips there.
[Magisk] exalented:
I could have sworn that I only updated the manager..

I have tried a clean install. That didn't make a lick of a difference last time.

I've just made a backup, so I'll get back to you on this.

EDIT: Tryed only updating the manager. Couldn't find fingerprint features in the settings.. looked the same to me.

Tried updating Magisk, but when I boot up again it shows that it's not installed. Flashed v14.2 for a reboot loop then flashed the uninstaller. Booted fine. Then flashed v14.2 to get to where I was.

EDIT 2: With a series of uninstalls and re-installs, I was able to get my ROM to boot with the new manager and binary, but I still don't see the finger print setting.
[Magisk] ToXiTe:
Why does Magisk Installer delete uci.sh script from my /res folder in the ramdisk during boot.img modification? I need it in the folder to get STweaks to work. If it is critical to remove this, please suggest a workaround.
[Magisk] NiTrOwow:
Installed Viper4Android today and updated Magisk toV15.3 passing SafetyNet

But after installing V4A AML v2.9 and V4A v2.5.0.5 I lost SafetyNet and magisk manager crashed (this was when I was on version v15.1).

After updating Magisk to 15.3 it passes SafetyNet again but the application I use ""Card Emulator" stopped working it says;

System partition is locked : cp: /system/ect/libnfc-brcm-20797b00.conf: Device or resource busy

So I dumped the logcat and searched for the package to see what happens, but nothing wrong shows up in there it says I get the toast and then cancel toast. So it does not log anything to logcat that is useful.

I tried system partition unlocking by Card Emulator but this didn't work, reinstalled and cache deleted. No change unfortunately. Any solution maybe? It's really wierd because I can open and edit the .conf file and all permissions of Card Emulator are correct :eek: Before I installed V4A and Magisk update to v15.3 it was all working fine.

Edit: I decompiled Card Emulator to see what happens. It seems to me that it is not able to properly mount system.

So here is where it fails ?

mount -o ro,remount
mount -o rw,remount

Edit2: I made Card Emulator a system application, and this also made no difference. I was hoping it would work as a workaround for now.
[Magisk] mctiew:
This is an android tv box, with the model name called x92. It is based on Amlogic S912 processor running amlogic reference design q201. The kernel may have been self compiled by the Rom creator.
[Magisk] robertbarber:
I am having an issue with Magisk not seeming to remember my root permissions I give to apps. For example if I give root permissions to Kernel Adiutor for it to work and then close out all the apps and then load the app again then i will get a popup asking me if I want to grant the app root permissions. Same with Matlog and any other root apps I have tried. I have attached the Magisk log and here is a link to the error I keep seeing popping up https://pastebin.com/i4s6Qdkh . My phone is an Axon 7 A2017 U version running the 1/15 beta version of Project New World an 8.1 Rom which if you need more info on can be found here https://xdaforums.com/axon-7/development/rom-project-world-t3728221 . I am running Magisk 15.3 and the Magisk Manager version is 5.5.5 . In the app it states that the latest Magisk version is installed and I can pass SafetyNet as well. I am running Stock Rom with Gapps from here https://androidfilehost.com/?w=files&flid=237585 and Magisk. No other mods are on the system and I have no Modules running in Magisk.
[Magisk] wineds:
Does Magisk 15.3 support microSD cards formatted as EXFAT? I get a SD corrupted message from my phone in this case. If I uninstall Magisk and reinstall SU I do not have this issue. Also If I reformat the microSD card in my phone it will format as FAT32 and I no longer get the SD corrupted message. microSD card is a 64GB Sandisk and phone is ZTE AXON 7 with AOSP Oreo ROM but I have also encountered this on ZTE stock Nougat ROMS.
[Magisk] Einsteindks:
Seems to be my issue as well. Droid Turbo, modded stock ROM. Been setting quietly, waiting for it to be resolved since everything else works ok.
[Magisk] Wolfblade1215:
Same issue. Same phone, rom and magisk version. I uninstalled and reinstalled magisk and that did nothing. Superuser log shows nothing.
[Magisk] Gen5:
Thanks for the link. Im still having trouble installing it. When i do a full unroot in supersu, i end up losing twrp (i chose the try to restore stock boot image and dont restore stock revery image).
[Magisk] teddy0209:
On some devices, restoring stock boot.img will trigger a restore of recovery upon reboot...
[Magisk] Gen5:
Do you know what i can do to install magisk? When i do a full unroot in supersu and dont try to restore anything, i get a failed install (due to a patched boot image). When i do a full unroot in supersu and try to restore the stock image, it restores the stock recovery.
[Magisk] xiiihyou13:
i think we have the same issue. any of you guys running F2FS as data partition?
[Magisk] Didgeridoohan:
Then just reinstall TWRP after unrooting...

Or, you can use the unSU script instead (you'll find a link to it in the link I posted earlier) and reflash your stock boot image before installing Magisk. All of this can be done in TWRP and you don't have to reboot in between.
[Magisk] ryuksniper:
hi, i have problem with safetynet, i have OP5T with OB2 oreo, with magisk 15.3 and xposed beta systemless and safety net not passed.

anyone know i resolve? thanks
[Magisk] Didgeridoohan:
The number of times it's been stated, you'd think that most people would have got it by now... :laugh:

You can't pass SafetyNet with Xposed active. And to answer a couple of common followup questions:

It doesn't matter if it's systemless Xposed, it'll still trigger SafetyNet.

You can deactivate the Xposed module in the Magisk Manager and reboot if you need to pass SafetyNet.

The point of systemlessness is not to pass SafetyNet (that's a happy little byproduct).
[Magisk] kosmatyj:
The Chineese guys integrated SU install in recovery as additional option an it works. They also have made .zip for flash via custom recovery because option "Install SU Root" disappears from menu if non-Chineese theme for recovery is installed. Here is some data you asked to send.

https://yadi.sk/d/Pqa1J0443RY8F7
[Magisk] TENN3R:
Guys I'm trying to create a module that replaces systemui

In oreo 8.1 qs background is semi transparent, now I *should* achieved how to make it solid, but I don't know how to build the magisk module

Any help? Thank you.
[Magisk] tys0n:
I tried with f2fs on my Moto G5 stock rom but modules not loading.

Workaround module didn't work either so I edit ramdisk to boot with ext4 and format data partition. Now all works :)
[Magisk] teddy0209:
Use the module template...
[Magisk] NiTrOwow:
Again after update from v15.1 to v15.3 hell brake lose.. Applications started to act wierd (Application with root access can't mount system and get "Device or resource busy" error).. I did a uninstall from Magisk manager and it it bricked(bootloop) my device AGAIN!

Had to flash boot.img from fastboot to recover it. Seriously, this isn't stable at all. Where can I find v15.1 ?

Edit: I downgraded to v15.1 and everything is fine now.
[Magisk] Didgeridoohan:
Isn't it better if you try to provide details and logs to help solve any possible issues?
[Magisk] NiTrOwow:
Where to find the log file? I tried to search the forums to look for it but I was not able to find it or do you mean logcat.

And also I just downgraded to 15.1 and lost SafetyNet again... I wish I never updated man, my device is bricked again. The uninstaller 20180113 script is stuck on "Restoring stock boot image", great!

Edit2: So..... After reflashing boot.img through fastboot and uninstalling and installing numerous times it seems to finally work again..

I bet you there's a bug in the update logic. Each time I update Magisk problems will occur!

PS Magisk-uninstaller-20180113.zip doesn't work (it will freeze at "Restoring stock boot image"). I had to use Magisk-uninstaller-20171226.zip. I uninstalled with TWRP and after that I reinstalled the latest Magisk again to see if it works somehow!?, and it really does now. Also the application that was not able to mount system works now and can read nfc config etc. Really strange this, also SafetyNet passes again. Updating Magisk from within Android fails each time, and then I need to fully uninstall and flash boot.img again through fastboot..

Edit3: So after installing Viper4Android in Magisk the problem occurred again! I'm not sure why...
[Magisk] Wolfblade1215:
My data partition is f2fs. Might try ext 4 and see what happens. That takes time though.
[Magisk] Artim_96:
If the kernel supports it. Otherwise you'd need a patched custom kernel or the Magisk module F2FS loopback bug workaround, it will basically move Magisk to /cache, which is normally ext4
[Magisk] Wolfblade1215:
You're saying I need either a patched kernel, that module, or to reformt my data partition as ext4? My cache partition is currently f2fs.
[Magisk] Artim_96:
Right. What suits you best. But in your case the module won't make sense since cache is also F2FS
[Magisk] Didgeridoohan:
Details should include device, ROM, any other mods running, etc. Logs could include installation log/recovery log, magisk_debug.log (you need to install the beta version of Magisk for that, no difference except more verbose logging), logcat, etc. Anything and all you could think of that would point to the problem. Since there seems to be issues with your boot image as well, a copy of the stock boot image might also be a good idea.

Depends on which one you're using, but some V4A modules changes a bunch of SELinux policies. That can cause issues...
[Magisk] Wolfblade1215:
Alright. Guess I'll just reformat as ext 4.
[Magisk] Wolfblade1215:
Format data to ext 4 and magisk should work properly. People in my thread have reported that.
[Magisk] Wolfcity:
My Moto G5+ has data partitioned f2fs and cache ext4. I use the latest loopback module which works flawlessly. I upgraded magisk from 14 to 15.3 with all modules. The mod also fixes the official TWRP on my device which wasn't able to hold any settings like language,read only or whatever. Some say f2fs isn't as stable as ext4 but it seems to be faster in read/write actions.