yashsingh1/xdaforums huggingface dataset:
[Magisk] prog-amateur:
Dear all,

I have a serious issue. By mistake, I have installed Magisk update on a wrong root image location ("sda" something), and now I can't boot anymore.

The situation is :

- impossible to boot (no Meizu logo)

- impossible to boot into recovery mode (volume up + power)

- possibility to boot into fastboot mode (volume down + power)

I think TWRP is no more accessible. Please, how can I recover my phone ?

Thank you very much for your kind help.

For you information :

phone : Meizu Pro 5

OS : Resurrection Remix

Recovery : TWRP
[Magisk] SolusCado:
Who are you responding to?
[Magisk] woozie.2007:
you my friend, i got that error too, but after i installed 11.6 and updated from manager, the safetynet seems to be ok now
[Magisk] SolusCado:
:) That's what I was hoping, but there are so many different issues being discussed here. I'm trying to find 11.6 now. Is there an official link with historical versions anywhere?
[Magisk] woozie.2007:
hmm, i saw was disappear now, i can't find it
[Magisk] Peeterz:
Anyone knows what causes my OnePlus 2 go into bootloop when I try to install Xposed through Magisk?

Only way to get out is to uninstall Magisk through TWRP
[Magisk] Didgeridoohan:
Just pop the file in post-fs-data.d and give it execution permission (chmod 755 should do it).
[Magisk] DeathHacker:
Can anyone confirm the problem that I'm having, as described in https://github.com/topjohnwu/Magisk/issues/313 ?

It seems that MagiskSU with the --preserve-enivronment flag doesn't actually preserve the environment as it should.
[Magisk] Rom:
So i must define the location instead of "${0%/*}" in post-fs-data.sh right ?

But how define the permission in the .sh file ?
[Magisk] Didgeridoohan:
I honestly have no idea what you are doing.

I thought you had a script in /system/etc/init.d that I suggested that you could test placing in /magisk/.core/post-fs-data.d instead. Why are you making a module?
[Magisk] Rom:
Ok, i would like to have an magisk module to put constantly the SELinux mode to permissive at each boot the most speedly as soon as possible.

As an "classic" magisk module, it toggle the selinux mode too many time after, so your idea about post-fs-data.d appear an good idea and i like to code even if i learn to make "basic" updater-script.
[Magisk] Didgeridoohan:
If I run the exact command you describe in that GitHub issue I get the same result, if that's what you're asking.

I have no idea what it means though... :D

---------- Post added at 22:29 ---------- Previous post was at 22:20 ----------

What happened with the init.d script you were talking about? :confused:

The simplest method to do that with Magisk is to put a file (name it whatever you want) in /magisk/.core/post-fs-data.d and put this line in it:

setenforce 0

Don't forget to give it permission 755.
[Magisk] DeathHacker:
Ok, thanks for testing. It basically means that one of MagiskSU's options isn't working as it should.
[Magisk] Rom:
Ah ok, i already know the command to put in it.

About the givven permission to this file, i must declare this in the config.sh file (at the end) ?
[Magisk] Didgeridoohan:
One more post, then I'm giving up...

I'm not talking about making a module. Just create the file I talked about in my last post and place it in the post-fs-data.d directory. Simple.

If you really, really feel you need to make a Magisk module you don't need to do anything else than edit module.prop and "MODID" (your modules id), "AUTOMOUNT" (set it to false) and "POSTFSDATA" (set it to true) in config.sh. After that you take the setenforce command and put it in the end of the post-fs-data.sh script, zip up your module and flash it. That's it. The above solution is simpler...
[Magisk] Rom:
Thanks.
[Magisk] prog-amateur:
Sorry but anybody knows how to do please ? I am blocked with my phone and can't do anything due to my mistake. Thank you.
[Magisk] DeathHacker:
Looks like you flashed over the wrong partition, although AFAIK it would affect either the recovery or the ROM, not both.

To reflash TWRP, follow the instructions at https://www.xda-developers.com/how-to-install-twrp/ under the "Install via ADB" section. Note that where it says to use "adb reboot recovery", you will need to boot into fastboot mode with volume up + power button instead.

Then you should be able to reflash the ROM from TWRP. Your data *should* be fine, but as I don't know what partition got messed up, I can't be sure.
[Magisk] Didgeridoohan:
Asking for help in your device's forums might be a better idea...
[Magisk] dvdhngs:
hello everybody!

someone could help me?

when i touch on superuser at side menu, show that magisk manager has stopped.

any ideia?
[Magisk] DeathHacker:
I don't know what causes it, but I had the same problem as well.

Because of another issue unrelated to Magisk, I ended up uninstalling and reinstalling Magisk + Magisk Manager, and the problem went away.
[Magisk] magisklover:
Is it possible to install Magisk on an emulator?
[Magisk] DeathHacker:
It depends if the emulator fully emulates the normal boot procedure of an actual device.

The answer is almost certainly no.

Even if it does, you'd need to flash Magisk to the boot partition somehow, which involves either:

a) booting into recovery (very unlikely for an emulator to have a recovery, as it doesn't require one; if you brick it, you can just make a new "device")

or

b) using something like FlashFire, which requires root, and depends on how the emulator handles rebooting/booting into recovery (also probably not going to work).

You essentially need a device emulator instead of an Android emulator.

Might I ask what emulator you are planning on using for this?
[Magisk] yochananmarqos:
No.

Emulators don't have a boot or recovery partition.
[Magisk] DeathHacker:
Wouldn't it be technically possible to emulate the entire flash chip (including those partitions) though?

Not that I can think of any emulators that do, but I'm pretty sure that's only because they don't have a good reason to. ("Normal" users don't care about rooting/TWRP/etc.)
[Magisk] yochananmarqos:
No, because an emulator is either using GRUB or a VM. Neither are setup for that.
[Magisk] DeathHacker:
Um... Virtual Machines can very well emulate entire disks, for example, Genymotion and Bluestacks both use VirtualBox under the hood, and VirtualBox uses disk images which are represented as physical disks to the guest OS.

Am I missing something here?
[Magisk] yochananmarqos:
Nobody said VM's can't emulate disk images. The point is, not a single Android emulator has a boot or recovery partition.
[Magisk] DeathHacker:
Well, I suppose no well-known ones are. I see your point. My point was it's possible for an emulator to have one, and I wasn't sure what emulator he was using.
[Magisk] Didgeridoohan:
This can usually be fixed by clearing data for the Magisk Manager.
[Magisk] RohitJainWorld:
If i update lineage os.

Do i need to flash magisk again?

Help!
[Magisk] Didgeridoohan:
If you're using v13.1+ you shouldn't have to, since it has addon.d survival support.
[Magisk] AnilRockstar:
I can't even pass basic integrity test on my Redmi 3s Prime with MIUI 8 , Magisk 13.3 and latest Magisk manager and a safety net solution module .

Please help
[Magisk] dvdhngs:
Thank you [MENTION=8248855]DeathHacker[/MENTION] and [MENTION=4667597]Didgeridoohan[/MENTION], I uninstalled and installed again, then worked, but on next time I will try just clear data.
[Magisk] teddy0209:
You have to use the SN fix beta5 test version... Magisk v13 won't work as is on MIUI...

Edit: you might need to remove previous installation of magisk, then reinstall along with the sn fix...
[Magisk] quebec1:
Hallo I have a question i buyed a honor 9. My phone is totally stock, now can I flash magisk for root my phone?

Sorry for my english
[Magisk] MichaelRector99:
Are you new to this?

If you are, I can help you...

PM, et j'te dis quoi faire.

J'te parle français, si tu connais pas bien l'anglais!
[Magisk] AnilRockstar:
so i have to use magisk 12 and sn fix ?

provide sn fix link and some instructions
[Magisk] AK2H:
Magisk doesn't work on (Galaxy A3 2017) running Nougat.

It used to work well on Marshmallow.

In Nougat after i flash the Magisk.zip and reboot I get stuck on boot logo and i can't even access TWRP recovery.

So I had to flash the firmware again vid Odin.

P.S. there are other users that encountered the same situation which was reported on A series 2017 Section.
[Magisk] prog-amateur:
Hi, thank you very much. It doesn't work (access denied), but as somedy said here, it is not a magisk topic, so I have asked the question in the Meizu thread. I hope somebody will help me to solmve this issue.
[Magisk] Danny94:
Looks like a new update rolled out - Safety net doesn't pass anymore on my phone.

Edit: "Only core features" fixed again.
[Magisk] :
Magisk Manager download and install modules but not the apps. Any light over this? E.g. Greenify4Magisk.
[Magisk] DodoGTA:
SafetyNet still passes on my device without core-only mode
[Magisk] Danny94:
[MENTION=6429309]DodoGTA[/MENTION]

well then i don't know what happens. I changed nothing today, not even rebooted or something else.
[Magisk] DodoGTA:
I attached some screenshots to this post to give you some proof
[Magisk] Danny94:
[MENTION=6429309]DodoGTA[/MENTION]

oh im still running 13.3. Maybe because of that ;D
[Magisk] Didgeridoohan:
It should work on v13.3... The Universal SafetyNet fix module thread is in the Magisk forum. It's not hard to find.

No. It passes on v13.3 as well.
[Magisk] Danny94:
[MENTION=4667597]Didgeridoohan[/MENTION]

well then sorry for wrong informations.
[Magisk] Didgeridoohan:
Not really no... It's hard to say what's happened without seeing some logs (recovery log from installing the module and a Magisk log, at the least) and possibly also the contents of the module folder under /magisk.
[Magisk] Legendary Cryptid:
So I recently downloaded the busybox module, v1.27.1. It says that it will be updated at next reboot. I've rebooted 10 times now, and it still says that. Any fix?
[Magisk] Didgeridoohan:
Flash in recovery instead.
[Magisk] Legendary Cryptid:
Problem is, I can't delete it inside the manager either. It won't let me.
[Magisk] Didgeridoohan:
You should be fine just flashing over it in recovery. If it still doesn't work, just delete the module folder in /magisk and start over clean from recovery.
[Magisk] Legendary Cryptid:
How do I navigate to /magisk?
[Magisk] Didgeridoohan:
Booted into Android, with a root capable file explorer. In recovery you need to first flash the Mount Magisk script from the Collection of Magisk modules v2. After that you can navigate to it using the recovery file manager.
[Magisk] Legendary Cryptid:
Well, I used Solid Explorer, found magisk in the root section, and just deleted the busybox folder. It worked.

I still get errors trying to flash Unified Hosts Adblock. I'll post my next log after this. If ot truly is a problem with the ROM, I'll have to flash stock and try getting the latest system update, then reinstall TWRP and Magisk and try again.
[Magisk] dratsablive:
Give it time, I was passing a few hours ago then all of a sudden it didn't. May take a while to reach you
[Magisk] :
How can I get a log from installing the module if I installed from twrp? I'm kinda noob with this but really want to make it work, I need Greenify and ViPER, but Manager doesn't install the apps, just the modules.
[Magisk] Didgeridoohan:
http://bfy.tw/DC4s
[Magisk] Darkaeluz:
So I've run in some trouble lately with magisk, it runs fine for a day after a boot but then I loose root and the manager refuses to open again and when I try to open it it just force closes and keeps doing that until I reboot my phone again, I've tried clearing the data of the manager, reinstalling it and reinstalling magisk.

Phone: Nexus 5

ROM: AICP

Android: 7.1.2

Kernel: ElementalX
[Magisk] paed808:
I also have this issue.
[Magisk] kwanthenewbie:
Wait, what? How did you get magisk 13.4 sir?
[Magisk] srk05:
What a tremendously frustrating experience. I get repeated problems with zip signature verification, and I can't seem to reach anyone who can clear this up.

---------- Post added at 03:48 AM ---------- Previous post was at 03:46 AM ----------

I thought that if I started with an absolutely absolutely stock HTC u11, I would avoid the problems that I had with my Nexus 6p, when I try to uninstall SuperSU and use magisk. I was wrong.
[Magisk] DodoGTA:
I'm a member of private Magisk Slack group, so that's how I got Magisk v13.4 before its release
[Magisk] ForgottenDude:
I had this issue today. Hoping it doesn't happen again.

FWIW, AdAway updated the hosts file in the background (and used su for it). Then half an hour or so later, I found that Nova Launcher was no longer using its root feature (screen lock). Opened Magisk Manager, and it crashed. Rebooted, and it got fixed.

Phone: Redmi Note 4 (SD)

ROM: AEX 4.4 (7.1.2)
[Magisk] darkshines87:
My Payback Pay and S Push Tan by Sparkasse don't work anymore. Any ideas how to fix this? CTS passes and Mario Run works.

Edit: Universal SafetyNet Fix also did not work
[Magisk] Didgeridoohan:
Details needed.

Grab a logcat from the crash.

Details needed.

Grab a logcat from when you toggle the hosts setting.

What a tremendously random post...

If you switch forums you're going to have to provide some details or you're not gonna get much help. Don't expect everyone to look up your post history like I just did.

Anyway... Looks like you're just a bit impatient, because you have several answers in the ViperU ROM thread with users/devs willing to help.
[Magisk] iamkevinhuang:
Magisk Hide doesn't work with my Digital Payment app on my phone...
[Magisk] otyg:
I have a china tv box (H96 Pro) and I used to be able to install magisk from the magisk manager since the device has unrestricted root (without a control, which is why I like magisk su) ,

but now with version 13.3 I get installation error! and it completely de-roots the device, also I have to use version 5.05 of the Magisk Manager to see the correct partitions like /dev/block/boot , 5.1.1 only show unrelated partitions, and autodetect fails to find...

anyways it worked flawless with version 13.0 but now I can't even install that one, is there anyway I can select the 13.0 zip on fresh install when I click download and install it automatically selects the latest magisk, I want to use a older version, I understand when magisk is installed previously you can flash in the modules sections but this is hidden on fresh install....

Please advise :), Oh and it has no twrp, and even if it did magisk cant auto detect the correct boot partition (/dev/block/boot)
[Magisk] f575gtc:
Hey everyone sorry but I am a bit lost on the install instructions

I am currently on a Nexus 6P running Pure Nexus Marshmallow I am planning on upgrading to Nougat, the instructions for Magisk state to flash to a stock rom and remove root then install Magisk so am I supposed to go from pure nexus to a stock rom removing root, install Magisk, root then go to Pure Nexus Nougat? Won't removing root also remove my access to TWRP? How is Magisk installed without root?
[Magisk] loadie:
The latest Pure Nexus N does not come with root so you won't need to unroot. You can still access TWRP without root.
[Magisk] f575gtc:
Is flashing to a stock rom first an absolute requirement?
[Magisk] Darkaeluz:
After I posted this I gave another try and uninstalled magisk and everything again, it stopped force closing the instant I open it just to FC Everytime I try to enter the superuser tab, here's the log.
[Magisk] loadie:
That would bring you up to the latest radio and bootloader but no, you will however need to do a clean flash.
[Magisk] f575gtc:
thanks I have a better understanding of the process now.
[Magisk] Didgeridoohan:
Just to clarify: the installation instructions mention restoring the stock boot image, not ROM. That means your ROM's boot image without any other root solution's patches.
[Magisk] NitsuguaIvo:
I've got a problem with Safety net. It says "the response is invalid"

I came from lineage add-on-su, then flashed the add-on-su remove file. Then I flashed magisk v 13.3. Did i do anything wrong?

Device: Samsung S7 edge

ROM: lineage OS 0618 (stock kernel)
[Magisk] kluczus:
I have a rooted LON-L29C432B225. Was trying Magisk 13.3 but without luck. Phone restarts automatically during magisk installation through twrp withou any information :(
[Magisk] zeon321:
Many google apps are force closing after flashing magisk, I tried wiping cache/dalvik but it doesnt work. I'm on lineage os 7.1.2 kenzo. Is it because im also using xposed framework?
[Magisk] Dc0de:
Maybe down to "webview". Check the troubleshooting guide mate for more info and report back if that fixes it. I'm pretty sure it's covered there.
[Magisk] TogoFire:
HTC M8 Unlocked S-OFF Android 6.0.1 Device

When installing magisk 13.3 my device will not turn on. I am using this boot img: https://xdaforums.com/attachment.php?attachmentid=3563978&d=1449164240

Source: https://xdaforums.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
[Magisk] Sascha1976:
Force closed
[Magisk] 4r44444:
Savety Net not passing tests... Honor 9 .... Universal Savety Net Modules neither fix it.... Using Magisk 13.3, newest Magisk Manager.
[Magisk] :
Here you have the recovery and Magisk Manager logs. Magisk folder under /Root just has the modules uncompressed.
[Magisk] gametimebrizzle:
Wasn't webview disabled in nougat by default?

I can't recall what the "replacement" was/is, but I can definitely attest to *my* Android System WebView being disabled with zero issues.

» Leedroid on HTC 10 [vzw] - Android 7.0

I remember reading about it somewhere, but I cannot remember where, so no sources unfortunately.
[Magisk] Pkt_Lnt:
http://www.androidpolice.com/2016/07/20/google-explains-chrome-will-become-webview-android-7-0/
[Magisk] gametimebrizzle:
How is it that you are running xposed on SDK>23?

It is my understanding that xposed is yet to be fully/officially Nougat compatible

---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------

That happened to me on (I think) 13.1...

I rebooted to recovery and restored boot.img and then rebooted and everything worked fine

---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------

*Check settings, is MagiskHide enabled? Sometimes gets switched off randomly.

*Toggle MagiskHide (off > on)

*Look at Magisk logs (inside Magisk)...logs are generally fairly helpful for troubleshooting
[Magisk] DeathHacker:
This is true, however there is an unofficial build for Nougat.

https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
[Magisk] Immortalis:
When installing Magisk 13+ on my OnePlus 3T and any module dropping files in /vendor, restarting the device causes bootloop.

No logs in logcat are thrown, just

CANNOT LINK EXECUTABLE: library "libNimsWrap.so" not found
page record for 0x7facbdf010 was not found (block_size=32)

No magisk_debug.log file too.

Also, when i mount magisk.img, TWRP shows "vendor" as a file, not a folder in modules folders, however "cat" refuses looking into it, as it's a folder. :eek:

EDIT: It seems to be a TWRP bug instead.

EDIT2: magisk_debug.log just showed up.

E/Magisk ( 454): mount /magisk/dap/vendor/etc/audio_effects.conf->/vendor/etc/audio_effects.conf failed with 2: No such file or directory
D/Cryptfs ( 463): post_fs_data done
D/Cryptfs ( 463): Just triggered restart_framework
--------- beginning of crash
F/libc ( 2570): page record for 0xf773f00c was not found (block_size=16)

No problems on G2 Mini.

Somebody knows what's wrong, and what steps I can take to fix this?
[Magisk] gametimebrizzle:
Right...but that is some hacked up quarter-port of Rovo89's source code, and I hear it's as buggy as my backyard in mid spring, so compatibility is a shot in the dark.

OxygenOS on Android 7.1 looks to be the original target of the port, (which is still not guaranteed to work even when on a OnePlus on OxygenOS running Android N 7.1) - and even if it does work, it's not *really* even Xposed when it's all said and done, it's a dangerous semi-port and can't be relied on (as [MENTION=4419114]rovo89[/MENTION] makes abundantly clear in the link provided).

But luckily, it's your own prerogative to flash whatever buggy zip you'd like to flash on your phone, regardless of the boldface warnings from the only true Xposed dev out there, [MENTION=4419114]rovo89[/MENTION].

It's just not worth the headache of fixing what it may break, but that's just my couple pennies worth.

edit: I keep adding to my posts vs replying to posts..:silly:
[Magisk] DeathHacker:
Yeah, I know, but it *does* exist, and that's the only way I can think of that he's doing it.

Would be nice to hear from [MENTION=4872843]zeon321[/MENTION] himself though.

I wonder if it could be possible that he somehow got one of the official Xposed builds (for <7.0) on Nougat, and could that be the reason why he has problems?

I haven't any experience with Xposed, so I'm not exactly sure this is even possible.
[Magisk] Legendary Cryptid:
Quick question: When flashing Stock ROM, will that remove Magisk root, but leave the manager intact?
[Magisk] gametimebrizzle:
* Go to Magisk Manager > settings > scroll to bottom

Is the "Re-Authenticate after upgrade" option toggled to ON?

if

NO, the turn it on, and force close root explorer, maybe clear the app's cache while you're at it (IDK if clearing cache makes a difference, but it won't hurt).

elseif

YES, navigate to the # Superuser section/drawer in the Magisk Manager and make sure the root permission is toggled to ON for root explorer.

Try again, hopefully it'll work now.

This is just what I would start with if I experienced your issue, it may not apply.
[Magisk] ~Qwerty:
Hi guys,

I keep getting root requests for random system apps, log says command: setenforce 1, I left Magisk on it's default settings and tried factory reset hoping to fix it but nothing helps, I'm using Xiaomi Redmi Note 4x running latest Resurrection Remix with the latest 13.3 Magisk version, the issue I'm facing is the exact same as the one on this link:

https://xdaforums.com/apps/magisk/apps-request-root-access-selinux-t3637866/post73292187

(Post labled: 'System apps request root access? Selinux? Setenforce?' on the first page)

Also when I check the Data usage for the system apps that had been granted root access they all use data through the FM Radio app for some strange reason, please help me figure it out because it's a fresh clean install and it's driving me crazy.
[Magisk] gametimebrizzle:
Magisk Manager is an app (apk) and Magisk itself is an image (.img) that lays on top of your system partition if I understand it correctly.

Magisk modules are stored in /sdcard/MagiskManager (internal SD card), so a dirty flash shouldn't overwrite that, but I don't believe it's advisable to dirty flash from custom to complete stock ROM (I'm fairly sure of that).
[Magisk] paed808:
It's the system settings app. But for some reason it's always a random system app. It's the SELinux toggle in RR settings.
[Magisk] Legendary Cryptid:
Well first, I'm still on Stock Rom. I'm doing this to remove TWRP temporarily so that I can update my software, as it is still on the November 2016 patch. Second, what is dirty flash? My phone's an LG K7 MS33010i firmware 5.1.1.
[Magisk] tansanrao:
Same issue here but with every single app trying to write to internal, magisk manager refuses to download modules too.
[Magisk] Diddymies:
full wipe and clean flash+flash magisk. Thats the only way. Magisk always have to be fresh from boot.