yashsingh1/xdaforums huggingface dataset:
[Magisk] alexpower:
Same behavior, lost root if a while in deep sleep.

Only reboot fix this.

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] Joshwaaa:
Has anyone been able to get this to work with LG V20 Verizon?
[Magisk] Shemploo:
How can I properly logcat things related only to magisk?

I tried adb -d logcat com.topjohnwu.magisk but there seems to be a lot more in there than just magisk.

Update:

Well call me Sally, I can't reproduce the "App Unchecking" problem anymore.

I unchecked everything under Magisk Hide, and rebooted a couple times, SafetyNet passes, AdAway works, I'm not sure what caused the bug I mentioned before.

I'm sure it's going to come back, how do I properly catlog ?
[Magisk] olivercervera:
lol I work at AirWatch (which is VMware now).

We added SafetyNet check since august, but it's not the only way we have to detect root. I did test Magisk v6 at the time of its release, and AirWatch was still able to detect root (other apps not).

If I have time I will test Magisk v9 with AirWatch and let you know :p I have a company phone, so I use that one for emails, no corporate stuff on my personal devices!

For me, the main thing is to use banking apps (Barclays Bank, Android Pay), and Magisk does the job since I discovered it (v6).

I also noticed that sometimes when I add an app to the list it's not being actually added. I discovered this by using magisk/.core/magiskhide/list. I eventually ended up using the /add command. It's not a big deal, but just wanted to report that sometimes the app does not do anything when adding an app to the whitelist. Logs don't show anything new.
[Magisk] dimm0k:
DELETED
[Magisk] Cinayet:
How about using MagiskHide on S7? I did cf autoroot, magisk + phh, supersu unroot and SafetyNet claims that my phone is modified. (supersu was installed in systemless mode)
[Magisk] ghbuur:
just tested airwatch container with magisk v9 and it detects root during setup. good for enterprise i can setup but after a minute it detects root too and gets disabled. magiskhide enabled and checked both apps. would have been nice..
[Magisk] olivercervera:
AirWatch Container and AirWatch Agent use the same SDK, so Agent will detect Magisk v9 as well. Good to know, thanks for the test :P
[Magisk] BashyFR:
Updated from v8 directly, G930FD (S7 dual sim) using android 6.0.1 and stock ROM XXU1BPHJ

Magisk Manager in Log shows :

Reboot did not solve problem.
[Magisk] Cinayet:
Same here.
[Magisk] Basic11:
I've gotten the Magisk v9 to work with SuperSu 2.78-SR3 and SuHide. But I can't disable the xposed systemless 86.6. I even tried 86.2 and still does the same thing.
[Magisk] thomasswan5547:
What device and rom, are you passing SafteyNet?
[Magisk] jcrompton:
Yes but to be honest I forgot which one but I did get it to work on one of the Nexus 6 7.1 ROMs
[Magisk] Didgeridoohan:
I opened an issue on GitHub about Magisk Hide and the "loosing root" problem. My knowledge around what logs/info could be useful is quite limited, so feel free to chime in if you've got something to add.

https://github.com/topjohnwu/Magisk/issues/14
[Magisk] jcrompton:
Sounds good -- I haven't had time to mess with it but unfortunately when I tried to flash Blackbird kernel after success with a PN based ROM (stock kernel) and then reflash Magisk and the superuser module I was not then successful --- granted it could be the kernel
[Magisk] dimm0k:
[MENTION=4470081]topjohnwu[/MENTION] or anyone! why do I keep getting "the zip is not a magisk module" when I try to add ANY module? my log doesn't show anything out of the ordinary... I have magisk v9, SuperSU 2.78-SR3, suhide .55 and everything is working fine except for adding modules. HELP!
[Magisk] jcrompton:
I believe the log here is what he needs
[Magisk] Trainer_Red:
I'm running Cyanogenmod 13 on my S4 and flashed Magisk v9 and Phh's Superuser and I'm getting "payload verification failed." Any help or do I just have to deal with it?
[Magisk] en11gma:
does magisk automatically decrypt data partition or is twrp needed for that or is there a magisk module?

when i check partition encryption with:

'adb shell getprop ro.crypto.state' = enabled

'adb shell getprop ro.crypto.type' = file
[Magisk] IronTechmonkey:
That lines up: Along the way core was updated but never uninstalled. Thanks.

As to how a hidden Magisk package is handled during an app or core update, it seems that Magisk can indeed handle that automatically, at least in some cases it may not matter. I've only been hiding Magisk for a few months but have been through at least two or three app updates and a core update. The first time I may have restored (unhidden) Magisk before the update but on a subsequent app update (prior to 26.4) I installed the update in place, IIRC without having to rehide. This time with 26.4 there was an even more direct comparison because I was updating two similar android 11 devices at the same time. After having the minor glitch that we are presently discussing I applied both the app update and the core update to the other device and did not have to manually unhide/rehide.
[Magisk] gloops100:
Hello all,

I'm on HyperOS (Xiaomi Fold 3).

I've disabled the "AndroidAutoStub" module in Magisk, on now I'm in boot loop...

I've booted in TWRP to disable the module, but I didn't find it (in /data)

Any solution please ?

EDIT :

SOLUTION FOUND !!!

I used the tool : payload-dumper-go_1.2.2

to convert the payload.bin to have the init_boot.img

flash the ini_boot.img with fastboot => Boot ! without data loss !!!! :) (except root)

When I try to ROOT again but flashing the init_boot.img and reboot ; then again the boot loop.

=> How can I disable this Magisk module that cause that ?
[Magisk] J.Michael:
I thought the decryption (or the not encrypting in the first place) had to be done when the data partition was wiped.

I have since read that some versions of TWRP are capable of dealing with the encryption: they do not decrypt the data partition, as in when they are done the data partition is still encrypted; they are able to read an encrypted data partition as well as the Android system is able.

I don't know that it has any effect on Magisk. Magisk piggybacks on the Android system, so when Magisk reads a file on the data partition, it probably gets decrypted automatically by Android -- provided you've entered the appropriate authorization.
[Magisk] J.Michael:
The Magisk modules are in subdirectories of "/data/adb/modules". Each subdirectory corresponds to one Magisk module. A module can be disabled by putting a magic file (or a file with a magic name) in the module's directory. You'll have to look it up -- I think it's ".disable", but I've never done it.

You make it sound like you used Magisk manager to disable a module, and you blame that module for the bootloop that didn't occur until after the module was disabled. If you really disabled the module, I don't think that can cause a bootloop.

Then you say you wanted to use TWRP to disable the module that you had already disabled. That seems pointless.

Did you ever restore the boot image that you improperly patched and flashed?

You say you recovered from the bootloop by reflashing the init_boot image. That makes me think that you damaged the init_boot image earlier, but you didn't mention that.
[Magisk] gloops100:
Normally I've disable it... Not sure what cause this boot loop.

I tried to delete the folder /data/adb , but it doesn't exist.... Very strange :

If I try to flash again the init_boot.img flashed with Magisk, I've a bootloop.

Now I'm on the phone, without Root or Magisk.
[Magisk] J.Michael:
I do not understand what that picture was supposed to show. It is not even showing that you have a "/data" directory, let alone that there is no "/data/adb".

You do not say whether you ever repaired the boot partition you mistakenly patched.

Does your TWRP have a file manager? Can you just look at "/data/adb/modules/screwymodule" and see if it contains a file named ".disable"?

Maybe your TWRP can't handle encryption. Or you didn't tell it to mount the data partition.
[Magisk] gloops100:
The /data folder ; should be in root partition ? (on the picture, I don't have the data folder)

Regarding the boot partition :

- I've took the original "init-boot.img" and flash it with fastboot

- Boot is OK now

If I flash this file with Magisk and install it with fastboot , the boot loop appears.

=> In TWRP I didn't find this path : /data/adb/
[Magisk] badabing2003:
It sounds like you have bad modules that are causing the bootloop.

You need to find a way to disable.

Safe mode should be the easiest, but if that doesn't work and TWRP does not decrypt data partition, you would need a special Magisk build that disables modules but keeps root.

Take a look at this.

GitHub - badabing2005/Magisk: Special Magisk with modules loading disabled.

Special Magisk with modules loading disabled. Contribute to badabing2005/Magisk development by creating an account on GitHub.

github.com

This is one specific Magisk version, you can temporarily use that version to fix the problem, and then go back to your version or you can take a look at the changes and apply the same on your desired version.
[Magisk] gloops100:
Thank you ! but what is the goal of this special Magisk ?

I'll already lost the root ; I need to root it again.
[Magisk] badabing2003:
You are in a situation where you need root to be able to disable the module(s) but if you aquire root, modules are loaded and you bootloop and don't manage to get to system to disable them.

This special Magisk does not load modules, but grants you root access, you should be able to boot to system, disable the module and then flash normal Magisk.

Obviously you want to enable back some of the module at that point but keep the misbehaving ones disabled.

Simply put, it is a special Magisk with root but without modules loading.
[Magisk] gloops100:
I tried but the process is not clear...

I've booted in TWRP and try to flash , but I don't have access to internal storage...

I tried : Wipe > Advances Wipe > "Data" > Repair or Change file system > Change File System > EXT2 ; then EXT4

Now I've boot loop on TWRP... how I can solve this please ?
[Magisk] J.Michael:
Did you change filesystem?

Did you wipe data?

DO NOT DO THESE THINGS NOW

Please just answer the questions.

What did you try to flash?

What does internal storage have to do with that?

If TWRP is bootlooping, you probably need to reinstall TWRP. Do you remember how you did it the first time?

The first step is probably making sure you can get the device into the mode in which you can flash. Not actually flash anything. Just confirm that your computer can "see" that your phone is connected. There is some sequence of pushing or holding buttons on the phone to put the phone in "download" mode. Just confirm that you can do that.
[Magisk] gloops100:
Did you change filesystem? => No

Did you wipe data? => No (just convert /data partition to EXT2 then EXT4 ; Youtube tuto here :

)

- I was unable to mount external storage (I was not able to see external storage) ; so I follow this guide above.

=> Decrypt partition ; put password (same as Android lockscreen)

I don't remember exactly, but not sure if I've flashed...

TWRP is working.

I remember how to flash it :

fastboot flash recovery_ab ./twrp_babylon_3.7.0-12.img

fastboot reboot recovery

ERROR on TWRP :

E: Unable to decrypt FBE device

If I want to change to SLOT B or A :

Error changing bootloader boot slot to B

Failed to mount '/bluetooth' (Invalid argument)
Failed to mount '/dsp' (Invalid argument)

PS : I've extracted all files from Recovery ROM (bluetooth.img ; dsp.img ; ..) if needed I can flash them.

Or there is something to do with the encryption data...
[Magisk] J.Michael:
I am not watching a video.

What "external storage"?

I don't know if "convert filesystem" is supposed to conserve contents, or just reformat. I don't know if encryption is preserved or all data is destroyed.

I think we are beyond "preserving data".

When you changed the filesystem type, you might have made it impossible for Android to mount the data partition. If you changed the filesystem type back to what it was originally, that might undo the damage. But there might be some ID number that has been irrevocably changed, and now the system will never be happy. Plus, we don't know what the original filesystem type was -- it might not have been ext2 or ext4.

Do not pull pieces out of TWRP ROM -- if you need to reinstall TWRP, flash the full TWRP ROM.

FBE is "File Based Encryption". I think the TWRP you have cannot handle encryption. I think whatever process you followed to remove encryption failed.

I think you need to find a thread about your device, maybe about your operating system, and see if someone describes a procedure for wiping data and disabling FBE.

I think you should start by flashing a stock ROM to try to get back to a working device.

Then find a procedure that claims to eliminate encryption. Until you have that, you can't use TWRP.

Or forget about TWRP. I think Magisk can exist with FBE. I just think you, again, need to find a thread about your device. Or at least find mentions of your device in this thread. Because it is important to know ahead of time whether some version of Magisk had a problem.

If you ever had Magisk installed, then you know a safe version. If you never had Magisk installed, do a lot of reading so you can pick a good version.
[Magisk] Mowca:
I can't configure Magisk-v26.4 - Android 11 Lineageos​

Hello

Samsung galaxy s10e

Lineageos 18.1

I reinstalled lineageos 18.1. Then I installed Magisk 26.4 from the apk file. when I run it it shows me:

Installed N/A

Zygisk N/A

Ramdisk NO

What do I need to do to configure Magisk correctly?

I followed this description:

Installation

The Magic Mask for Android

topjohnwu.github.io

-> Custom Recovery

I extracted the boot.img file from my rom: lineage-18.1-20210909-UNOFFICIAL-beyond0lte then:

Copy the boot/init_boot/recovery image to your device

Press the Install button in the Magisk card

If you are patching a recovery image, check the “Recovery Mode” option

Choose “Select and Patch a File” in method, and select the boot/init_boot/recovery image

now I have the file magisk_patched_[random_strings].img, and what now ? can I flash it in twrp?
[Magisk] J.Michael:
When you say you "installed from the apk file", do you mean you installed the apk file? And when you open the Magisk manager app that you just installed, it says Magisk is not installed?

If so, that all makes sense. Installing Magisk is another step.

I don't know what you can flash from TWRP. It's possible that if you rename (or copy) the magisk.apk to magisk.zip, that you can then flash it in TWRP. It's also possible that it will fail. Only one way to find out.

You parroted general instructions that covered at least six possible configurations and then said "now I have the file". You need to say which options you used so someone can scream "Not *that* way!"

I think the choice between boot and init_boot is, if your ROM has an init_boot partition (I'm not clear whether LineageOS is free to have an init_boot independently of whether the stock ROM had one), then you patch that. Otherwise you patch boot. If you have replaced recovery with TWRP, you don't want to patch recovery. I think you do not want to patch recovery unless you have a device/ROM that forces that on you.

You should really look for a thread with people who have installed Magisk onto LineageOS on a Samsung Galaxy S10E.

Did you use Odin to install TWRP? I would expect you to use Odin to "flash" a magisk-patched boot image.
[Magisk] en11gma:
sm-g985f/ds on Android 13 (WI7) rooted with magisk 26.4 and debloated with adbappcontrol 1.83. disabled 10 apps (mostly updaters) and uninstalled 227.

ok i think i got everything working perfect. (i havent checked everything such as sim slots or ext sdcard that goes in sim tray.) but no errors and its fast.

i am so fast with doing fresh install of stock firmware and install magisk 26.4 i dont even care that the File System is encrypted.

it would be nice to do full backups and i think there still might be away through adb or ssh but i dont even care.

magisk is a patcher right?

let us have selinux=permissive.

i have a feeling this isnt hard to do when magisk manager is patching the original AP file to make it flashable.

if someone knows how and just dont want the whole world to know just tell me how to do it in a pm.

please.
[Magisk] J.Michael:
Magisk manager doesn't patch the original AP file to make it flashable. The original AP file is already flashable.

Have you tried taking a Magisk patched image and unpacking it so you can explore the initrd?

android-x86 has a kernel command line parameter "SELinux=permissive". Maybe a piece of the boot image has a recognizable kernel command line (or at least the parameters) that you could edit.
[Magisk] en11gma:
i think it does.

when i look at the boot.img, and vbmeta.img that is in the newly created magisk-patched.tar those are for sure modified and not like the orig.

ive use 'diff' and xdiff to compare.
[Magisk] en11gma:
on my sm-g985f/ds s20+ (exynos) Android 13 WI7 10-01-2023 security patch level magisk 26.4 works great.

i have no issues.

if i download twrp 3.7 apk and install it can it install the twrp recovery without problems?

i have serious problems getting it to work correctly.

also what about multidisabler?
[Magisk] Nergal di Cuthah:
Such a specialized question would probably best be answered by your device's board on xda. Twrp is kinda device dependent, i would assume especially for samsung since there's probably knox involved in the mix (in the past samsungs were tamper trapped with fuses blown and bricks hard, i don't know if that is still true).. I don't actually know what multidisabler is
[Magisk] majorfigjam:
Deleted 27 /12 /24
[Magisk] hanschke:
New Canary build available but I lost root. Patched the init Boot and flashed it but after booting No root available.
[Magisk] J.Michael:
Did you ever hide the manager app?

Did you unhide before installing a new apk?
[Magisk] sawdoctor:
What device and android firmware? Might help narrow it down
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (65207f96) (26404)​

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w

Diffs to v26.4​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

https://github.com/topjohnwu/magisk-files/blob/2b3030fba9f24a6eeb148527d2d8cce7b294609e/notes.md

👍 PW
[Magisk] hanschke:
I have done the Update from the manager and after that i have patched inside the boot img and done the reboot.

No root and I have taken the init boot and patched it. Boot into fast boot and flash it with adb and start the Phone.

I use my Pixel Fold with Android 14 qr2 beta
[Magisk] sawdoctor:
I'm on the pixel fold running qpr2 beta 1.1 and was about to try the update. Can you downgrade/, install the previous version of Magisk canary?
[Magisk] martyfender:
I have had no success getting root on any version newer than aa6c7c15 26401. in every newer instance I have unhid the manager, then tried the direct install. So I update the app, then magisk it self and I notice the patching goes by to quick, as if it failed.

upon reboot I do not have root. In each of the newer updates I then tried patching my boot.img and then flashing it in bootloader mode with fastboot. this always fail to give root so reverting back to aa6c7c15 26401 always give me root.

Onn 8 1st gen, Android 9.

I don't believe I get any useful logs from this. Has anyone else had this issue?

Thanks

The log is attached for the last working version. As far as I can tell, no logs are created for the recent failed versions. The last log in cache also was aa6c7c15 26401.
[Magisk] hanschke:
@sawdoctor

do you have the older apk please? I dont have made an backup.
[Magisk] sawdoctor:
I have the previous apk, i know you can rename it to .zip and flash with magisk but never tried doing it with fastboot. I always use pixelflasher for flashing
[Magisk] hanschke:
thank you now I have root again :)
[Magisk] sawdoctor:
So that version worked but latest didn't? And renaming it to .zip and flashing with fastboot worked? Just want to double check everything before I try as we have the same device. Might be worth posting a bug report on GitHub see if anything comes from it
[Magisk] hanschke:
Thats right this version from you worked fine
[Magisk] Wotanstahl:
Hello, i just installed lineageos 20 on my Samsung Tab S5e. Now i need Magisk for "Viper4Android" (with lineageos, the built in speakers of the tablet sounds awful).

Since the bootloader ist unlocked of course, is there a chance to install magisk without wiping data again? i just set up everything already.
[Magisk] zulu88:
As far as I know, there is no such option and never has been.
[Magisk] Lord Sithek:
you should be able to flash Magisk in TWRP
[Magisk] zgfg:
Magisk installation does not wipe Data, and never did

Unlocking Bootloader wipes data (Factory reset) - but that's not Magisk installation

User needs to unlock BL only once (it will wipe the Data).

After that he can install/uninstall Magisk as many times he wants, but that would no more wipe his Data
[Magisk] Wotanstahl:
that sounds good. Do i even need twrp or can i just use the custom recovery from the lineageos-installation?
[Magisk] pndwal:
... But this is a Samsung device...Official instructions still say:

I don't know if Samsung devices need this extra wipe when using custom ROMs however, or when installing as .zip via custom recovery... Likely this does make a difference and there may be documentation for rooting LineageOS / other custom ROMs...

Mmm... But again, please note these caveats for Samsung:

... So these notes preclude both flashing stock (unpatched) AP binary (ie. restoring stock, unpatched images) and uninstalling Magisk (which is the same thing) as full data wipe may then be needed to recover...

Again, I believe this doesn't cover custom ROM/recovery use, but you'll need to research...

🤠 PW
[Magisk] Lord Sithek:
Im not sure, I've never used LineageOS recovery but I have this tab and flashing Magisk from TWRP certainly works
[Magisk] hanschke:
https://github.com/topjohnwu/Magisk/issues/7659 I have tried to do an issue but invalid bug report. WTF
[Magisk] sawdoctor:
I guess the bot won't accept a bug report unless you try with the latest debug build and upload the log? @pndwal might be the best person to ask about it
[Magisk] pndwal:
Yup, follow template for required logs/Magisk build...

Basically, having "Magisk version code: 26404" in text body will bypass bot closing as invalid...

If you don't supply logs from Debug build (has verbose logging), eg if you use Canary, Stable etc, they'll smell a rat and chastise you anyway! 😁 PW
[Magisk] hanschke:
Thank you for the information.
[Magisk] sawdoctor:
Do you know if anyone else has reported the same/similar issue with latest canary in all the groups your in? Wondered if it was an isolated case.

Thanks for the reply and thanks for everything you do for the modding community too 👍👍👍
[Magisk] pndwal:
So this

... No, may be isolated issue... Some A13 LV devices have issues with Zygisk (broken) for Stable Magisk, and recent refactoring (move to native bridge loading, built in late Canary) fixed this... May be a regression that shows up in the P Fold... That move was a big one w/ work beginning in March and NB-Z is still considered beta...

Would be good if one of you makes a valid issue with logs... They may defer it for a while in case it's due to some inconsistency with beta ROM however...

Please make sure root is really lost, not just issue with Magisk App, eg conflicting hidden stub App (often found in system settings, Apps, and solution is simply to uninstall)... Check for binary (version) installed or running daemon version from a terminal emulator:

magisk -c
magisk -v

👍 PW