yashsingh1/xdaforums huggingface dataset:
[Magisk] Ibuprophen:
My deepest apologies for this post!

This was meant for another thread and (as Bugs Bunny put it) "I, somehow, took a wrong turn in Albuquerque"... LMAO! :)

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] peterlee928:
[MENTION=4470081]topjohnwu [/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] and all the other brilliant minds - just saying much thanks for yalls tireless work on advancing magisk. v16.6 works seamlessly thus far on my p2xl (stock rom, no custom kernels or tweaks).
[Magisk] salimskiy:
Hello. Sorry for the bad English. The problem is the following. The phone Samsung Galaxy A8 + 2018 Android 8.0 security patch July 1. Not installed Magisk v.16.0. Installed v.16.6, the root appears, but the cellular communication disappears, flies, I delete the magisk and everything is fine . On 7.0 such problems were not. The kernel is custom.
[Magisk] DroidJP:
The way i did it that works involves steps in a particular order

1. Get your stock boot image from your rom for your device. When you are about to patch it. Make sure preserve force encryption and preserve avb 2.0/dm-verity boxes are checked and begin the patching.

2. Boot to twrp, wipe/factory reset device

3. Flash Magisk but don't reboot once this is done.

4. Manually flash your patched boot img like you would flash zips. Be sure to switch to install image and look for the boot file. Select boot partition and swipe to flash.

Reboot and enjoy your fully encrypted rooted device :)

Keep in mind that once the data partition is encrypted, twrp can no longer mount data and you are pretty much stuck with that boot image until you factory reset. Updates to magisk are ok though. So no problems updating. Just not in twrp.
[Magisk] RiTCHiE007:
Need HELP please!! I had magisk installed on my oneplus 6 and due to a battery drain i had to flash the stock rom on top over my old install. The stock rom replace the boot image and after reboot i was not rooted no more so i did the boot from fast boot with modded boot image and the phone booted up but when i open up magisk manager then it says "installed" but only shows the uninstall option on the screen and no other option so i cant seem to patch the stock boot via magisk.

I have uninstalled the manager etc but after installing it again it shows the same every time.... So how do i i delete the magisk settings so that it install fresh on my phone?
[Magisk] Didgeridoohan:
Did you change the boot image format in the Manager settings? Did you try by leaving "preserve dm-verity" unchecked?

Mido device? You might need a custom Magisk version for now. You'll likely find it in your device's forum.

Enable data/wifi and make sure that nothing is blocking data for the Manager.
[Magisk] pythonimus:
Xiaomi Mi Mix2 with LOS 15.1 (2018-07-09), no custom kernel. I cannot find acustom Magisk version for this device.

EDIT: This works for me: https://github.com/Jerry981028/Magisk
[Magisk] :
The format that Magisk Manager choosen was .img. (As my stock ROM file have the boot image file)

I tried leaving the second checkbox unchecked, but verify error still appear.

But I saw it in Odin:

+ Before flash: Both System status and Current binary are Samsung official

+ After flash: Current binary become Custom.

Warranty void is 1

My system was fully stock before I flash Magisk.
[Magisk] martyfender:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Or here on github:

https://github.com/topjohnwu/MagiskManager/releases/tag/v5.8.1
[Magisk] GryphonBR:
Lg V30+ running BoomBox v1.2, essentially a debloated version of the original firmware. I reported on a previous version an issue with WebView's zygote crashing after updating to Magisk 16.6, issue still present. Attaching log of the occurrence, and reporting that downgrading to 16.4 solved the issue (albeit with root loss occasionally).
[Magisk] pythonimus:
I have this problem still on 5.8.1

Logcat attached:

1. rebooted my system

2. started magisk manager and did a SafetyNet check (both failed)

3. toggled "Magisk Hide" setting to off, and then to on

4. SafetyNet check again, both passed
[Magisk] salimskiy:
Help please ??? When installing Magisk 16.6 flies imei.Magisk 16 is not installed at all.
[Magisk] guest4711:
Sorry, I don't get your point. Please tell us on which device and which ROM you are and what's going on. Best is to submit logs (magisk log, recovery log e.g.)

Edit: There is still a problem with screenshots on XDA. They are not displayed...
[Magisk] salimskiy:
ok now I'll do
[Magisk] salimskiy:
Missing imei after firmware magisk
[Magisk] salimskiy:
07-12 12:33:18.908 2857 2857 I Magisk : ** Initializing Magisk

07-12 12:33:19.694 2857 2857 I Magisk : * Creating /sbin overlay

07-12 12:33:19.698 2857 2857 I Magisk : * Mounting mirrors

07-12 12:33:19.698 2857 2857 I Magisk : mount: /sbin/.core/mirror/system

07-12 12:33:19.698 2857 2857 I Magisk : link: /sbin/.core/mirror/vendor

07-12 12:33:19.698 2857 2857 I Magisk : bind_mount: /sbin/.core/mirror/bin

07-12 12:33:19.699 2857 2857 I Magisk : * Setting up internal busybox

07-12 12:33:19.785 2875 2875 I Magisk : Magisk v16.6(1662) logger started

07-12 12:33:19.786 2871 2871 I Magisk : Magisk v16.6(1662) daemon started

07-12 12:33:19.794 2871 2877 I Magisk : ** post-fs-data mode running

07-12 12:33:19.796 2871 2877 I Magisk : Create /data/adb/magisk.img with size 64M

07-12 12:33:19.850 2871 2877 I Magisk : * Mounting /data/adb/magisk.img

07-12 12:33:19.998 2871 2877 I Magisk : * Running post-fs-data.d scripts

07-12 12:33:19.998 2871 2877 I Magisk : * Running module post-fs-data scripts

07-12 12:33:19.998 2871 2877 I Magisk : * Loading modules

07-12 12:33:19.999 2871 2902 I Magisk : * Starting MagiskHide

07-12 12:33:20.000 2871 2902 I Magisk : hide_utils: Hiding sensitive props

07-12 12:33:20.000 2871 2902 I Magisk : hide_list add: [com.google.android.gms.unstable]

07-12 12:33:21.101 2871 3077 I Magisk : ** late_start service mode running

07-12 12:33:21.101 2871 3077 I Magisk : * Running service.d scripts

07-12 12:33:21.102 2871 3077 I Magisk : * Running module service scripts

07-12 12:33:56.574 2871 2902 I Magisk : proc_monitor: com.google.android.gms.unstable

07-12 12:34:24.937 2871 2902 I Magisk : proc_monitor: com.google.android.gms.unstable
[Magisk] salimskiy:
Here are the screenshots
[Magisk] RichardEb:
Since the last Magisk-App update the safetynet test reports false. Is this a Bug?
[Magisk] Salty Wagyu:
Could the inbuilt auto-updater be fixed? It keeps telling me a new MagiskManager apk is available but downloading from the notification or via the app does nothing.

https://imgur.com/a/D1p0j6D

edit: Added imgur link of 3 screenshots. XDA Attachment manager isn't working.
[Magisk] RichardEb:
Checked again...Now it's true again...strange
[Magisk] lop1:
I tried to install autowaze but if failed with :

- Copying zip to temp directory

- Installing AutoWaze-v0.7.zip

*******************************

Please install Magisk v15.0+!

*******************************

Failed!

! Installation failed

I am with magisk 16.6

Thanks

Envoyé de mon SM-A320FL en utilisant Tapatalk
[Magisk] guest4711:
Something is terrible broken on XDA. When downloading your zip, I get always 162 bytes containing a 403 - forbidden error message.

Your logs seems to be fine, I don't see any problems.

But if your IMEI is lost, something must have been gone totally wrong. This information is stored at a (protected) place normal flashing should not touch. Ask in your device forum if and how to fix it, please.
[Magisk] alroger:
Great. Install the whole Magisk thing correctly and you will be able to switch SELinux on and off.
[Magisk] Äptiva:
Reflash the rom and kernel without booting. Use adb or unSU to remove root and flash magisk all in one go. When you reflash the rom, can you wipe /system on your device safely? I'm only asking because I'm not familiar with newer Motos as the last one I used was the Droid X 2.

If so wipe data, cache, dalvik, and system then reflash.
[Magisk] arsenal3010:
Hi everyone,

I try to flash Magisk-v6 using TWRP but not successful.

I said Failed /system could not be mounted

I attached 2 images.

Any help is really appreciated

Thanks !
[Magisk] Äptiva:
Screenshots don't help. Post the recovery logs please.
[Magisk] gocats7:
Works great. I have searched the thread and found that it seems a lot of people have the same problem I am seeing but I haven't found an explanation. Trying flashfire, just sits at a black screen. I assume it's just not compatible because of how root works in the case. Can someone elaborate? Having this and flashfire would be perfect.
[Magisk] Emisand:
Ok, so I wiped data, cache, dalvik and system.

Then reflashed the stock rom, and twrp, booted directly into TWRP and ADB sideloaded Magisk v6, it installed, but then when I tried to reboot into system I got the exact same problem.

It boots into bootloader, bootloader log says "Boot up failed".

Only way to get it to boot is to flash the stock boot image again.

Please check the boot images I shared in my original post.
[Magisk] Äptiva:
Nothing I can do with those sorry. I only have a couple of LG G2s and Samsungs to tinker with. You'll want to post kmesg or dmesg
[Magisk] arsenal3010:
I used vi recovery.log to check the log and captured log' s photo since I cannot transfer recovery.log to my computer

Please help me to check. Thank you
[Magisk] rollerce:
First Problem: It's unrooting itself at boot when I'm using PhhSU and Magisk.

Second Problem: The SELinux toggle with magisk only works after boot. It doesn't persist and I need it to happen ON BOOT.
[Magisk] b00tstrap:
The only time I've seen the "SU binary out of date" notification is when something has gone wrong and the root mod isn't getting mounted. Can you post your magisk.log please?
[Magisk] b00tstrap:
Here's my ViPER|Atmos port that includes all the "surround" profiles for ALSA. Let me know how it goes for you (I haven't extensively tested it, and the port is in alpha, so expect things to not work).

No, each zip stands alone. ViPER|Audio contains the ViPER4Android apk and driver, along with ALSA and some additional libraries. ViPER|Atmos has all those things plus Dolby Atmos (libraries and apk). For the Atmos version, you can do things either through the ViPER4Android app or the Dolby Atmos app--whichever you like better.

I would NOT install both zips--that will probably break things (unless you put a "disable" file into one of them post-install). The alpha0.2 version of ViPER|Atmos here will disable ViPER|Audio if it finds it.
[Magisk] Äptiva:
No. Actual logs not screen shots. Upload them to google drive with your phone and link them.

---------- Post added at 12:58 AM ---------- Previous post was at 12:55 AM ----------

The first issue is strange. Can you toggle it at all?

The second issue you're facing is beyond Magisk and is a kernel or rom question. If Magisk is working then that question should be taken to the appropriate forum for your kernel or rom.
[Magisk] arsenal3010:
Is it recovery.log ?
[Magisk] bass122:
I have note 7.

ROM: TEKXodus Hybrid N7 URv2

Kernel: HydraKernel V1.2.5

I can use toggle root but not SELinux.

But when running some games still show " illegal........"

Is there a way to hide the phh's superuser?

I try to disable it but still the same.
[Magisk] pitsch1:
How can I install this on a verizon s5? In order to have safestrap, I have to root and it says not to root in the instructions, or do I have to go through unlocking the bootloader, dev version.? I upgraded to BOD5 and Lollipop 5.0. Going back to KitKat for now until I can get more info, any help is appreciated.
[Magisk] Äptiva:
If a failed flash recovery.log If magisk issue post boot, magisk.log and if bootloops kmesg and dmesg
[Magisk] -Happy Feet-:
Today I have try to flash the Elitekernel but I got an Bootloop when I flash the magisk mod again. But when I don't do this I have no root. Only the stock kernel works on my Xperia Z3
[Magisk] SkylinerzEx:
Does this work with Asus Zenfone 2
[Magisk] arsenal3010:
Thanks, it failed to flash, so I attach the recovery.log

Please take a look. Thanks !
[Magisk] lover:
I have thensame device and ROM did you find anyway to not get bootloop?
[Magisk] abbots:
Latest update is working ok, thanks.
[Magisk] salimskiy:
imei flies only after firmware Magisk on 8.0.Na 7.1.1 there were no such problems. The modem patching does not help.imei is returned only after removing magisk.
[Magisk] Comby_sk:
1. uninstall magisk manager app

2. use magisk uninstaller in Twrp

3. install magisk 16.0 zip in Twrp
[Magisk] mobilizmo:
Why don't save latest Magisk Manager (and earlier version too) its settings, such as dark theme, update channel, enable fingerprint authentication, etc...

Xiaomi Mi A1, AEX 5.7
[Magisk] wes'side:
Sometimes that happens when games don't like magisk and sometimes the way to get around it is to hide them using dotmod ,zuper to name some good ones to try out but you have to have xposed in order to make it work correctly without recognizing the magisk, for example using dot mod go into hide apps select magisk,hide from your app causing issue,and do this again as a precaution and its worked for me hands down, do it again but hide the app causing the issue from magisk,make sure to apply after each bout. Should solve problem unless xposed doesn't work on your device then try virtual xposed or systemless xposed. If all else fails then heck someone else with a better idea and or a second opinion if I'm not on the right track.

---------- Post added at 05:36 PM ---------- Previous post was at 05:27 PM ----------

Remove both manager an framework and that sometimes dies the trick if not what did you addb on your phone last sometimes magisk doesn't like that an as a lastbtesort,

Try a clean format or your phone if necessary, don't just wipe it,format it dry an start anew I know its not the best solution but a fresh start corrects the error.
[Magisk] Artim_96:
Then post that question to whoever asked it, not me. I'm not the one having a problem
[Magisk] djstone86:
[Help] how to restore my stock boot .img?

Long story short my USB C port no longer works for data transfer and for the headphone dongle (charging works). I went ahead and troubleshooted it by cleaning it out, using multiple cables etc, etc. My question is this: because I stupidly did a factory reset before I restored my boot.img is there a way to extract one from the stock google images and into a folder so that when I "restore images" it restores my stock IMG? Thanks.
[Magisk] dumbl3:
AdAway breaks my safetynet pass. Then I found out about systemless hosts option in magisk, but if I turn it on in MagiskManager preferences and I run safetynet test it doesnt work, when I turn it off, it passes the test again. Is this a bug, isnt systemless supposed to be 'undetectable'? I dont know really though, but can anyone help? I have been trying to figure out how to block ads and still pass safetynet so my bank app works (with magisk hide).

Running redmi note 5 pro global (whyred), unlocked, magisk rooted, AOSP extended v5.7

Edit: Just enabled systemless hosts & installed Unified Hosts magisk module then rebooted, and now i still pass the safetynet test. So that's good enough I guess :)
[Magisk] jcmm11:
The boot image? Yes. Just open up the zip from Google and you should see the boot image there. You can get it from either the ota file or the full factory image file. I forget, without double checking, if, in the factory image, the boot image is in the outer zip or the inner zip - but it's definitely there. Name will be boot.img

(Don't grab the bootloader by mistake. And that's definitely in the outer zip).
[Magisk] djstone86:
How would I be able replace the boot.img on my device?
[Magisk] wes'side:
I still cant seem to get the check safety net to worked,hasn't since 5.7.0 /16.4 or 16.0, when my phone restarts the manager switchs back everything set from dark theme,toasts on or off ,grant with permission is back to ask etc but still maintains root, everything seems to be in order otherwise on a nexus6p with fire hound 4.6,elemetalx,xposed the woiks.?

---------- Post added at 08:11 PM ---------- Previous post was at 08:08 PM ----------

Find it online, flash it when your in recovery mode. Not sure how it would go unless you do a clean wipe an start fresh.
[Magisk] martyfender:
You will never pass safetynet with xposed installed. If xposed is the systemless version with the module, I believe you can temporarily disable it to pass safetynet, though, if I am not mistaken.
[Magisk] Didgeridoohan:
If you still have a custom recovery installed, flash it there. But beware, if you flash a stock boot image, on the next boot the custom recovery will likely be replaced with the stock recovery and you won't be able to install a custom recovery again without root or through a wired connection to a computer.

If you don't have a custom recovery installed but you still have root, you should be able to use the TWRP app to flash the custom recovery and then you're good to do whatever you want. But beware, if you flash a stock boot image, on the next boot the custom recovery will likely be replaced with the stock recovery and you won't be able to install a custom recovery again without root or through a wired connection to a computer.

If you have neither root or a custom recovery installed you're likely out of luck unless you can get that USB port fixed.
[Magisk] andrew2432:
What device, Samsung Knox is tripped by nearly any bypass.
[Magisk] :
I do not talk about Knox, thing I want is Magisk works without formatting /data.
[Magisk] borgib:
Has anyone gotten this to work with Citrix Xenmobile? I saw some posts about it here but they happened a long time ago and I haven't seen any updates.
[Magisk] andrew2432:
So the release thread says flash magisk before a kernel. But some kernel threads say to flash the kernel first, then magisk. Should I defer to the specific kernel threads dev? If I need my stock boot image for kernel install can I just flash the magisk uninstaller and assuming my stock image was saved correctly it should be ready yes?!
[Magisk] BillGoss:
If the kernel is supplied as boot.img then you flash it before Magisk. If it's supplied as a zip file that uses the AnyKernel.sh script to modify an existing boot image, then flash it after Magisk.
[Magisk] elwhiteboy01:
I hate to be a little off topic, but I have a device that will never get a firmware update running KitKat. I would love to see magisk compatibility with KitKat one day.
[Magisk] eliezerjk90:
Guess it won't happen. KitKat only run on small fraction of devices and might be dropped soon anyway (because the users change phone, etc). It makes little sense to develop something that's already 5 years old and would probably last only 1-2 years to come...
[Magisk] gothicVI:
Find a custom ROM?

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] pythonimus:
Following my problem: https://xdaforums.com/showpost.php?p=77051432&postcount=25815

I think I know what the problem is here, persist.magisk.hide is deleted on reboot.

When I create persist.magisk.hide and set (to 1) with MagiskHide Props Config I pass (sometimes) SafetyNet check on reboot, but somehow its not fast enough (?) so the Playstore checks safetynet (and fails) before Magisk can pass it...
[Magisk] 3dawg:
I've been having a serious battery problem with Magisk.

If I use magiskhide to hide my banking app, my battery becomes absolutely crippled by a process called logd which afaik is necessary for Magisk to keep track of apps enabled in magiskhide.

I've read that disabling logd (android logging?) results in magisk hitting the cpu heavily instead and thus not fixing the problem.

Is this a bug or intended behaviour? It makes using magiskhide cost too much in battery life to be worth it.

UPDATE: It turns out that the logd process goes nuts regardless of whether an app is ticked or not in the magiskhide list. Just having magiskhide enabled in the settings causes the logd process to go haywire.

If logs or anything would help then please let me know. I hope there's a fix for this because it makes using magisk a bit of a nightmare on OP3!

Thanks.
[Magisk] yochananmarqos:
AnyKernel2 modifies the ramdisk only so it's fine to flash after Magisk. A few examples are ElementalX, Franco and Flash kernels.
[Magisk] Curtis20112:
How do I tell of magisk is fully uninstalled? For whatever reason when my device restarted to update a module it never started back up. Some Android error so I did a factory reset and my phone kept root through the reset. Phone was working fine again. Woke up this morning and downloaded a magisk module. When it restarted to install it it wouldn't boot past the recovery "no command" screen. Where I couldn't do anything so I flashed the stock firmware from flash all.bat which failed about 3 times it eventually worked. Phone is up and working without root this time. I just want to make sure I'm full stock and magisk is gone before I install a custom recovery and re root. Bootloader has stayed unlocked through this entire thing.
[Magisk] Artim_96:
Flashing stock ROM had removed everything Magisk needs to work since it will have replaced the manipualted boot.img.
[Magisk] Curtis20112:
Just wanted to make sure because bootloader is still unlocked
[Magisk] Karls0:
Is it possible to hide root for cloned app? Xiaomi devices has the ability to clone apps and games. Let's say I have an app which required unrooted device. On the "original" one I can add it to MagiskHide list. But what about the copy?
[Magisk] RiTCHiE007:
Thank you bro! I was indeed in flightmode and after turning on data i got the whole menu again so i could patch boot image so thumbs up for helping this noob :)
[Magisk] jcmm11:
If you want to make sure that all remnants are gone find the unsu zip by osm0sis and flash that. That+ stock kernel will definitely do the trick.
[Magisk] Artim_96:
Locked/unlocked bootloader has nothing to do with that. To even be able to lock it the OEM has to somehow deliver a signed boot.img. Motorola for example doesn't so bootloader can't just be locked by flashing stock ROM, only through some hacky methods.

If you want to lock your devices bootloader, your devices forum is definitely a better place to ask
[Magisk] DarkusRattus:
Hey, so I noticed that after I updated Magisk to 16.6, all apps that Magisk is hidden (via MagiskHide) from don't seem to open at all. (ex. PlayStation Vue, Pokemon Go, some banking apps)

Does anyone have any ideas on what I could do to fix this?

Edit: I just downgraded, and I also missed the part where this was a beta. Oops.
[Magisk] xunholyx:
Yes you can add it
[Magisk] d.terenzzo:
Dear dev, sorry if its a reported bug, but I didnt find it using search tool (tried to find "Mute" and only found "mate").

I have a capricorn (Xiaomi Mi5s) device and I was running AOSPex from [MENTION=7838323]Hlcpereira[/MENTION] (https://xdaforums.com/mi-5s/development/rom-aospextended-v5-x-t3773328) with all magisk manager and modules running flawless, then I upgrade the ROM from 5.4 to 5.6 and got a strange mute bug, the speaker stoped to work at all. I've tried few solutions from the ROM thread but i got no lucky, I fixed my phone flashing a [MENTION=5075128]LuK1337[/MENTION] LOS 15.1 ROM (https://xdaforums.com/mi-5s/development/rom-lineageos-15-0-t3667210).

Everything was running fine then I decided to install magisk and Bang! i got the same mute bug like before. Uninstalling magisk, fixed it (on LOS Rom).

Now, I'm here to report it and willing to help if anyone else is already helping.

If you want, just guide me to provide more and accurate information.

Device: Capricorn

ROM: LOS 15.1 build 07/09

Stock kernel

Gapp nano

Clean install

Magisk 16.0

Magisk manager v5.7
[Magisk] martyfender:
I want to report a Magisk bug:

Magisk logs are placed in /cache/magisk.log

If you face any issue, please upload /cache/magisk.log

Starting from v16.6, /data/adb/magisk_debug.log is NOT USED anymore!