yashsingh1/xdaforums huggingface dataset:
[Magisk] MithunSanthikumar:
Someone please explain this.

I have Poco f1 with LOS16 and is encrypted. Recently I flashed a new build of LOS and I saw some error message during magisk install at the end. So I had to reinstall magisk. But the "preserve force encryption" option is checked.

So how can I disable it and do I have to. I mean if try to flash a new build of LOS again the rom, it will re encrypt on top right?

Or can I just untick that option and flash magisk again through manager? Will that lead to unrecoverable data?

No matter how hard I try I can't get my head around this magisk and encryption issues that I encounter.

so please help. ??
[Magisk] Artim_96:
Well, you can control keepforceencrypt and keepdmverity through a .magisk file in cache.

And no, just flashing a new version of LOS doesn't do anything with encryption, completely different partitions. But if you want to switch ROMs you always should do a clean install, which included a wipe of /data. But that wouldn't remove encryption, it might only remove enough so the system don't know what actually the encryption password is.

It will tell you so on first bootup, but I'm not sure how it will play out. I use protected bootup where you have to enter your lockscreen password to fully boot Android, but I'm not sure what would happen if you don't use that.

Either way, if you only change /system, /cache and dalvik-cache you should be good to go. If you do more, be prepared that you'll need a factory reset
[Magisk] MithunSanthikumar:
What about updating vendor partition? Will that cause encryption issues? LOS16 won't flash without flashing the latest vendor files made by a developer from latest miui beta versions.
[Magisk] Artim_96:
Only the data partition has anything to do with encryption. The vendor partition is pretty much like the system partition, so something that's r/o either way
[Magisk] MithunSanthikumar:
So going by what you say there won't be any effect on the encryption status unless I change rom, I was planning to untick that option and update Magisk to latest version through Magisk manager. Then later flash LOS latest build.
[Magisk] BHUSHAN7988:
Have a question

Have OP6T, stock OOS, Magisk 19.2, Edxposed, TWRP 3.3.1-6

Due to Google server error I uninstalled magisk and installed it again.(via inbuilt app by doing complete uninstall)

To my surprise I did not lose the TWRP so only flashing magisk 19.2 got me the root back.

Now I have a question that haunts me!

Will the OTA update method of magisk work for the next update?

Will it restore image to stock OOS recovery?
[Magisk] bohemist:
Installing Magisk via Magisk Manager app does not touch TWRP. That is why you still have TWRP.

OTA, on the other hand, will overwrite TWRP with a stock recovery. In your case, as well as mine, OOS will overwrite TRWP with OOS stock recovery.

But there is a Magisk TWRP retention module you can install when installing OTA. I haven't tried it yet.
[Magisk] Salmin:
MIX3 MIUI 10.4 by xiaomi.eu 9.5.30

Magisk 19.2 (19200), MagiskHide Props Config 4.0.3-v56

Google Pay doesn't work. For a month now...
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] Artim_96:
Well, if you're disabling keepforceencrypt, that won't do anything unless you decrypt your phones storage by formatting the whole /data partition. That setting only prevents the phone from re-encrypting
[Magisk] qwer222:
Hi, what I want to do is patch boot.img into boot.tar, because I only have original boot.img, not .tar file. If I patch boot.img, output will only be in .img format.

In magisk manager 7.1, it still offer to output format to .tar file show in below attachment, but this option totally missing in magisk manager 7.2, while I can't use manager 7.1 because it will always force me to download and update to manager 7.2
[Magisk] Manish48:
[/COLOR]Hii i am unable to flash Dolby atmos zip file its displaying error magisk.img mount failed. I am using redmi note 4 with lineage Os 15 and magisk. Flashed the zip file through latest twrp. I am including screenshot and log file.

https://drive.google.com/file/d/1BZcZZrYJ2tzGBvHw6UZ-UuZsYjErwJyA/view?usp=drivesdk

https://drive.google.com/file/d/1Ub2tipAoPNWsFIAE9DuU8TNfy7c-mdav/view?usp=drivesdk
[Magisk] qwer222:
Hi, what I want to do is patch boot.img to boot.tar, because I don't have original boot.tar file. If I use magisk manager 7.2 to patch boot.img, output will be in .img format too, which can't be use by Odin.

In magisk manager 7.1, it still have option to choose output format as show in below attached print screen, but I can't use 7.1 because it will always force to update to latest version of magisk manager which is 7.2.
[Magisk] Didgeridoohan:
The module needs to be updated for image-less Magisk.

As far as I know (I don't do Samsung), the option isn't needed anymore. Just select your file and go for it... The Manager will take care of the rest.

If things don't work, you should consider collecting logs and opening a GitHub issue.
[Magisk] jcmm11:
This thread might help. https://xdaforums.com/showthread.php?t=2446269
[Magisk] st3venhall:
Word for word, step by step, and I'm golden! Vzw HTC 10 running Viper 3.1.0, was using SuperSU that's baked into the rom for awhile just fine, which was SuperSU 2.78 systemless. I tried the Supersu Magisk method from another forum with failure , so I decided to try this! This is a complete recreation of the tutorial above, I'm just going to be very specific.

Ran validator app, noted any directories. proceeded with full root uninstall through the Supersu app, then rebooting to twrp & running UnSu.zip, then making sure to clear out all the suggested directories from validator app via TWRP. I found none left behind. Then rebooted & uninstalled Magisk app & Xposed installer. Probly could have done that first. Rebooted recovery, uninstalled Magisk and Xposed framework using uninstallers. Rebooted recovery. Installed Magiskv6, Phh superuser 17 zip, and systemless Xposed 86.5 for Magisk. Rebooted system, installed Magisk Manager, Phh Superuser from play store, and Xposed installer by DVDAndroid in that order.

This part seemed important: opened Magisk Manager, toggled Root status to "off" in which I was prompted to Grant magisk manager su permissions, granted. Also important, i then went into Xposed installer and toggled the framework status switch (top right of installer app) to the off position. This disabled Xposed which would trip safety net if left on. MUST reboot to apply the changes.

Once I came back into my system after reboot, I took an extra precaution by clearing the app data of Android pay through settings. Just in case it remembered my false safety net status. I loaded up Android pay and was able to add a card and use it, no problem, for the first time. I wanted to write such a specific account of what I did because often people (like me) miss the little things... like reboots, or the little tiny switch to disable Xposed within the installer, which can really make the difference of success or failure.

All the devs involved in this are so amazing for dedicating what little time they have to helping us, and the less time we spend repeating questions is time well spent on brilliant updates and concepts like Magisk and Xposed, along with what I find to be a very exciting path of breakthroughs for systemless root development, you guys are freaking geniuses and humble ones at that. We users appreciate everything you do more than you imagine, and one of my favorite parts of the day is loading up XDA labs and seeing which threads have got new dates in the title, and that is my two cents!

Excuse the run-on sentences and excessive use of commas, (<-) I guess Magisk has just got me excited! Peace!
[Magisk] joshuaw84:
Don't forget SU app from playstore, if you forget this app he will have the same symptoms as not removing previous root.
[Magisk] JuergenZ66:
you don't need both, either SU app from playstore or unSU.zip, they do the same job.
[Magisk] Azuritko:
I have Sony Xperia Z1 Compact. I have flashed stock ROM 14.6.A.1.236_R6D using FlashTool. I have unlocked bootloader using FlashTool. Nothing else is installed. No recovery, no root...

Can someone tell me more deeply what to do now to safelly install Magisk and PHH Superuser and Xposed for my device? I can not figure it out and I have read that after installing not modified Magisk I can brick my phone.
[Magisk] joshuaw84:
No, I was meaning not having phh su app from playstore will have the same symptoms as not fully removing cm's root. He didn't mention downloading it when he said toggle didn't work...
[Magisk] Hyflex:
I actually managed to get it working last night to an extent by manually deleting left overs.

I just did it again using the instructions given.

Reflash cm

Reflash gapps

Reflash unsu

Reflash magisk

Reflash phh su

Reflash xposed

Reflash viper4android

I had already installed the phh superuser app and magisk manager.

So while the toggle works... I downloaded safety net helper and the validation fails.

What am I missing?

Edit: so it looks like xposed is now detected, uninstalling it males safety net partially pass with the exception of cts profile which I assume is because I am on cm? Right?
[Magisk] AmbientLights:
Safety net blocked Xposed recently
[Magisk] Hyflex:
Yeah just figured that bit out

Uninstalling it males safety net partially pass with the exception of cts profile mismatch which I assume is because I am on cm? Right?
[Magisk] joeyddr:
It worked fine for me.
[Magisk] JudgeDread11:
Osm0sis, who created the unSU script says in his thread that he did so because (older version of the SuperSU app did clean up well enough.

So it might not always be the same.
[Magisk] :
Hi, can I have the updater-binary script that you edited?
[Magisk] kunkka7:
Hello, still no way to get magisk to work on galaxy s2? Stuck in the bootloop after flashing it, flashing the uninstaller make it work tho.

Will v7 be released soon?
[Magisk] JikannoKami:
Yes I just did

I just did on my Oneplus One and everything is working nicely (even pokémon go):

I flashed CM14 (Unofficial)

Booted and configured my settings

Full unroot with super su and rebooted to recovery

Flashed magisk v6 and phh's superuser 17

Rebooted, installed phh's superuser (from Google Play) and Magisk Manager apk (donwloaded)

Best
[Magisk] Hyflex:
You passed the cts profile check on safetynet?
[Magisk] sino1641:
Doesn't support f2fs.

When I flashed magisk ,it didn't boot up.
[Magisk] Tkbf:
Finally, after hours of study, I am on magisk for the first time, and also phh's systemless root as well, nothing to say but they are just awesome!

Although I noticed there are known issues for Samsung device with V6, but there are also a few posts saying they installed magisk on their sammy successfully, so I decide to dive in and give it a try.

The software config. of my Note 4 N910U before the switching is the same stock MM rom PH1, SuperSU systemly rooted, and Wanam's Samsung Xposed.

In order to roll back to totally stock and unroot, I wipe the system and reflash PH1 rom via Odin, intentionally keep user data intact, then I flashed magisk, phh's superuser and topjohnwu's Exposed as instructed, no boot loop and perceive nothing abnormal. I re-enable all Exposed modules in the new Exposed Installer and reboot, everything goes well as they supposed to be.

Thank topjohnwu's excellent work, it's always so wonderful that we general user have you dev guys here to bring all these magic, like **MAGISK**, to us as real thing. Thank you. :good::good::good:
[Magisk] KenNashua:
Same issue...no touch screen after install of v6 along with the phh-superuser zips.
[Magisk] ALcAtRas500:
On cm 13 i can't flash the v6 zip. It says can't mount boot. Device is explay fresh
[Magisk] Mart1neZ:
Hi

I am getting response payload validation failed when running safetynet test in safetynet helper. Maybe some app i installed caused some change in /system so is there any way of resetting /system?
[Magisk] JudgeDread11:
Dirty flash your ROM, and remove baked in root afterwards if there is any.
[Magisk] FoOlKeN:
Anybody find something???
[Magisk] Simone98RC:
Hi guys,

I'm running OxygenOS v9.0.2 with Magisk v19.2, my device is a Oneplus 3.

The boot time is extremely long: after typing pattern, the decryption screen lasts almost 30-60 seconds.

According to Magisk log, every time I reboot there's a "su: cannot find manager" warning followed by the installation of Magisk Manager apk.

As attachment there's the full Magisk log, tell me if you need a logcat record.

Thanks in advance :)
[Magisk] JudgeDread11:
You forgot the attachment of think ;)
[Magisk] will5:
Hi guys. Can I get some help or ideas about this?

Im using sixaxis controller app. On lg v20 990ds android 8.

When using magisk, sixaxis app says cant configure/ failed to configure bluetooth.

When using supersu, it works.

What can be different from magisk and supersu that makes sixaxis controller app dont work?

Im using method 2 connection type on sixaxis controller settings. Its the only method I got to work on supersu. With magisk none work. Tried magisk 16, 18, 19, 19.2.

Thanks.
[Magisk] Ch3vr0n:
What's different? Oh just about everything regarding gaining root access to using that access once it's granted
[Magisk] will5:
Hi. Both supersu and magisk have root permission enabled for sixaxis app.

With supersu, sixaxis app works. With magisk doesnt (cant configure/failed to configure bluetooth error)

Im trying to make it work with magisk.

Something about magisk affects bluetooth on this app.
[Magisk] Didgeridoohan:
Your log makes me believe that the boot stages are quite broken on your device. I would try a complete uninstall and reinstall of Magisk, possibly even the Canary release to see if the current code base works better.

It's an old app that could have things specifically coded for SuperSU... It'll probably need an update. (which is unlikely to happen).
[Magisk] Simone98RC:
I've done the following steps:

1) Run of Magisk Uninstaller script;

2) Dalvik/cache wipe;

3) Re-flash of OxygenOS v9.0.2;

4) Reboot to recovery itself;

5) Flash of Magisk v19.2;

6) Flash of Magisk modules;

7) Reboot.

However, I get the same situation.

Ps actually I can't diagnose with an unstable canary build of Magisk, I hope it's not a strictly needed.
[Magisk] Didgeridoohan:
To get to the bottom of things, it is. Improved code and better logging (you'll have to use the debug build).

Edit: By the way... Have you made sure it isn't one of your modules causing it?
[Magisk] daaaquan:
Has anyone be able to get the Jack in the Box app working? I've tried hiding root from it on 3 different phones and it always crashes right at start up but works fine on my phone that doesn't have root.
[Magisk] linuxares:
Anyone happen to know if I just need to install Magisk as normal and get it to flash Oneplus 7 Pro? Or do I need to use those pre-made patches? I rather let magisk take care of it since then I know it's right.
[Magisk] Artim_96:
Those are questions that belong in the devices forum. Or just try it out. As long as they don't do anything strange there shouldn't be a problem. But you might want to force forced encryption and especially dm-verity to be kept, e.g. by modifying boot.img in Manager. They are the most likely reason you'll get into a bootloop

---------- Post added at 23:36 ---------- Previous post was at 23:31 ----------

What jack in the box app?

If hiding root from it and hiding magisk manager won't help and if apps like RootBeer Sample can't find anything that's not hidden you might want to try modules like the MagiskHide Props Config, that have advanced methods
[Magisk] Ahmetay:
Hello everyone,

i'm using an 5.1.1 tablet w/ Intel SoFIA c3230rk (wifi only) x86 chip.

so, i installed magisk with patching boot.img from magisk manager and flashed it through fastboot, cause i can't run any twrp images, just black screen..

and got magiskhide and su, but i can't see any of installed modules but a module named "img", i didn't install it, it was there since i flashed the boot.

and when i tried to reinstall magisk directly from manager itself, it says "Unable to detect target image".

and when i look at logs, i see:

and i installed stericson's busybox to xbin, so i can install modules, they are working but i can't see or manage them from magisk manager
[Magisk] ss.toedjoeh:
hi [MENTION=4470081]topjohnwu[/MENTION] , I've test ur latest magisk, when I try to patch the boot image in realme 3 pro (RMX1851) with magisk, the result is smaller then it used to be, it seems the ramdisk in the boot.img doesn't properly unpack/repacked? from 65MB original boot.img the result is 13MB patched boot.img?

in case u need the boot.img for test, here it is :

https://drive.google.com/file/d/157gd8IeGe9DRnn-aMUGKho77E0hVMmsG/view?usp=sharing
[Magisk] martyfender:
I'm on Intel x86 Cherry Trail Atom x5-Z8350 devices with Android 6.0.1 and saw that error on a past Unofficial or Canary build, but I don't remember which one without reading back in several threads. [MENTION=4470081]topjohnwu[/MENTION] was quick to fix that. I very rarely ever have "stable builds" on my 5 devices, as I am a tester. Is this with the latest released Magisk version, 18.2 or is it an older version? Can you provide a magisk.log as an attachment, or a link to a file sharing site such as pastebin?

Don't post it in the body of the thread, as it makes it difficult to read, especially for mobile users and clogs up the thread.

The preferred method to install busybox is with the magisk ndk busybox module, but I understand why you can't, of course. That error message is from magisk's own built in busybox, I believe.
[Magisk] Verequies:
Well I finally got around to trying this, and it seems that did not work. Still got the 'production build' error issue. I've been doing a lot of modifications and it'd help greatly if I could just adb push.

Also I have another question, how would I let apps like Kodi access the root folder?
[Magisk] martyfender:
On one of my devices a few weeks ago I tested adb root. I used the root app selinux switch to make the selinux state permissive, check the notification box in this app, also. On the adb insecure xda forum I downloaded a user modifed version that is supposed to work on some newer versions of Android to get it to work. On that version the apps window quickly closes on me, but stays open long enough to first grant root, relaunch it and check both options grant adb root and apply on reboot. You may have to open it several times if the app closes on you to confirm that the options are still checked and to get them to stick. It may work on your device without the app closing, like on my Android 6.0.1 device.

https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502

https://xdaforums.com/showthread.php?t=1687590

Here is a link to the modified version:

https://nofile.io/f/86605d8qsJs/adbd-Insecure-v2.00.apk

If you have problems with usb debugging getting disabled, read the the adb insecure thread. I had this initially but eventually got rid of it with the help of selinux switch to set selinux permissive.

Disclaimer this method may only work on some devices, use at your own risk.

I don't need adb root most of the time, but I tried to help someone in the past with it. I keep it on that one device to test with newer Canary versions to make sure it continues to work. So far, so good.

With the help of others in the adb insecure thread, some knowledgeable and industrious individual may be able to improve on the modification. If anyone tries this, I would suggest getting permission from [MENTION=631273]Chainfire[/MENTION] . I'm not sure if the modified version in the thread was done with his blessing, or not [MENTION=631273]Chainfire[/MENTION] 's last update for the original version, was for compatibility with Android 5, I believe.

The modifed version is for up to Android 7, if my memory serves me correctly. Maybe I overlooked it, but I don't believe you noted your device and Android version.

Good Luck.

UPDATE: for selinux switch to work you must turn of Google Play Protect. Even with this off you will still get warnings and enforcing will be enabled on a reboot. In the warning notification, press and hold to get a popup to allow the app anyway. See my last couple of posts in the selinux switch thread for details.

Maybe any further discussion of this should be posted in the above mentioned threads as it is getting off topic in a Magisk help thread?
[Magisk] Verequies:
Ah alright, I'll give it a shot. My device is a NVIDIA SHIELD TV 2017 16 GiB @ Oreo 8.0. The same issue also happens on my Axon 7 @ Oreo 8.1. I just don't understand why its only a problem if I have Magisk Hide enabled.

EDIT: I tried the above method, however it still didn't work. At this point I'm willing to believe adb root will only work with Magisk Hide disabled.
[Magisk] Unit ZER0:
I'm running this ROM: DeluxeROM 4.2 [Oreo] for the SM-G935F (https://xdaforums.com/s7-edge/development/sm-g93xf-deluxerom-v1-t3832610), and the last build I can run on my device is 18.1. None of the 19.x builds will work, and all attempts to update have resulted in loss of root. I can install and run the latest version of Magisk Manager with no issues, add modules, and complete all other operations without incident.

Device: SM-G935F

CUP: Exnyos

OS: 8.0.0

Kernel: 3.18.122-morokernel-oreo-v4.6

Build Number: R16NW.G935FXXU3RL3

EDIT: Found a solution! You must update this ROMs Kernel to the latest release (MoroKernel 6.1) (https://xdaforums.com/s7-edge/development/23-04-17-morokernel-1-6-g93xf-t3594754) to use Magisk 19.2
[Magisk] KitsuneFoxy:
Hi, is there an archive of the removed modules? O still use some for my old phone. I looked t the GitHub and they are all gone. Was there a backup?? I was using some ios stuff, the keyboard typing noises. Etc [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] martyfender:
If the module has a thread, you can often find a link for it there. If you post the module names, sometimes users who still have copies will attach them for download. Finally, you may possibly be able to contact the author if you know who did it, to get a copy.

[MENTION=4470081]topjohnwu[/MENTION] gave the authors plenty of time to update to the new template before he removed them. I believe in some cases they were removed because they did not conform to certain other requirements of what a module should do.
[Magisk] svcopio:
Hello

I have installed magisk manager on my device found and patched a stock boot image of my device flashed it with fastboot but magisk manager is still showing me not installed. Pls help i dont know what to do.

My device is Infinix x625b
[Magisk] garylawwd:
Is magisk manager installed on external storage?

If so move it to internal storage
[Magisk] VampiruX:
Thank you Tylerhole, but how do you do that ?
[Magisk] BernardJake:
PROBLEMS

Hi!

After installing Magisk my camera stops working. I've tried using other versions of Magisk, change permissions of the Build.Prop and nothing to go back. But if I enable the "Core only" option of the Magisk, everything works perfectly. (But I can not use the modules.)

Can anybody help me? I use this cell phone in my day to day life, I really need it to work perfectly.

Hugs!
[Magisk] guest4711:
So probably one of your modules is broken. Disable one by one until your cam is working again. Then you know the culprit... (Don't forget to reboot after disabling!)
[Magisk] BernardJake:
But i don't have any module installed. :/

Anyway, I tried a lot of versions of Magisk trying to solve the problem.

Please, help. :(
[Magisk] tylerhole:
Check your messages