yashsingh1/xdaforums huggingface dataset:
[Magisk] adhammagdy:
Magisk prevents my phone from powering off

Please help..

I have Lenovo p2 phone with stock 7.0 rom rooted with magisk latest version..

magisk works correctly and everything works.. however when I turn off my phone it' s still on..

when I power off, the screen goes dark, the phone vibrated once and turns off as usual... but when I try to turn it on I have to keep the power button pressed for 10 seconds to do a hard reboot because it's still on.. and if I turn off the phone for a few days I find the battery has depleted...

this also happened on Lenovo vibe p1 with aex nougat rom...

When I disable magisk or make it core only mode the problem goes away and the phone turns off and on normally..

I even used magisk after a factory reset and later flashed a custom kernel and still the problem persists...
[Magisk] Xtriel:
You read my logs?
[Magisk] madbat99:
F2fs loopback bug. You need a custom kernel or patched boot.img to fix it. There is also a module to fix it.

It's common on moto devices with f2fs data partition.

Try this
[Magisk] Wildchild0369:
Do you have the name of that module? I thank you enough
[Magisk] RogerF81:
I can't download files and apps with Magisk 15.0+ installed. Downloads from Play Store and browsers fail to 99% on my OnePlus 5. Which logs are needed to be able having a look into this issue?
[Magisk] DiamondJohn:
I upgraded from the previous stable magisk to 15.2, and I just checked my phone, and I have both paths of /data/magisk & /data/adb/magisk. I just checked, and the /data/magisk is a symlink to /data/adb/magisk

I am guessing I should not delete the "old one" /data/magisk, just for cleanliness?
[Magisk] Jamoeda:
This happens with me on my oneplus 5T and I can't fix... :(

---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------

My Op5t have the same issue and the partition is ext4... You can help? I ask for help some but the issue continues...
[Magisk] jenslody:
Do you have any modules enabled in Magisk ?

If not, did you try to switch off magiskhide before shutdown ?

And of course: logs, logs and again .... logs !

You can run logcat from computer via adb while shutting down.
[Magisk] Wildchild0369:
Fix it by flashing a custom kernel bro, Find one for your op5
[Magisk] spawnmhsbc:
I follow OTA installation tips and installed Jan security update for pixel xl.

1. Disabled system updating

2.use magisk v 15.2 uninstall to stock images

3.sysyem update to 1/6 in step one, problem happened

As per ota installation, I cannot reboot, if do thus, I don't know what will happened.

So how can I update JAN sec patch? Thank
[Magisk] Ingenium13:
I believe it's because dtbo has been patched. What I did was use fastboot to flash the stock boot.img and dtbo.img from December, and then adb sideloaded the full OTA. Without restoring the stock dtbo image, it wouldn't even let me flash the full OTA. It gave me AVB errors.

Unfortunately, magisk manager 5.5.3 seems to have a bug and patches dtbo after several reboots, even when "preserve AVB 2.0" is checked. So until that's fixed, if your dtbo gets patched, you'll have to reflash the stock dtbo image to upgrade. There is an unofficial version of magisk manager on xda somewhere that has dtbo patching removed, if you want to switch to that until the official one is fixed.
[Magisk] Eversmile23:
Help me.

Hi OP,

I had rooted with magisk, version 15.2(beta) installed. I wanted to experiment with a mod fron the XDA-developer. My device is with S-On. When I flashed the zip, and tried to activate through terminal emulator, I get a message that "sh : applet' not found. I had flashed busybox by Osmossis. I had asked the question in the forum for the mod, but I did not receive satisfactory help. I had used the same 'mod' previously on my older android mobile without difficulty, of course it was rooted but not with 'magisk'. Plz guide me.
[Magisk] jenslody:
[MENTION=8365819]sandaljrpit[/MENTION]: I just tested tcash wallet and the only thing you need/can to do in magisk is to add it to the magiskhide list.

It checks some flags, like build-tag, and some paths to check for su-binaries, some installed packages (not MagiskManager!, so no need to hide it), but it also checks the default properties by reading '/default.prop'. In my case it stopped because of 'ro.debuggable=1' in default.prop, even if getprop returns '0' for 'ro.debuggable', set by magisk(hide).

I had to edit the '/default.prop'-file to make it work.

Therefore you need to remount '/' with 'rw'-flag.

Unfortunately that does not survive a reboot, because default.prop resides in the boot-image.

So you have to change it after every boot, or write a script that patches (or replaces) default.prop on every reboot or change it in the boot-image.

On your device the cause for the not working tcash wallet might be different, but you should be able to find it with logcat: 'adb logcat -s RootUtil' only shows the relevant entries.
[Magisk] madbat99:
It's at the end of my post. Click the word "this"
[Magisk] RamHa:
Hi, im quoting part of OP and asking for explanation - what does it mean???

Quote " These beta releases are built with the debug flag enabled, so keep in mind that it will do a

lot of verbose logging

. " .

thank u all :fingers-crossed:
[Magisk] Legendary Cryptid:
Since v15, every time I flash a new version of Magisk, the manager doesn't automatically install. I have to go ino the zip and install it manually. Please fix this issue.

LG K7 MS330

SDK22

Lollipop 5.1.1
[Magisk] samosaara:
When he compiles beta magisk builds into binaries he explicitly makes then output much more information to logging when running, because beta builds obviously tend to fail much more often, more detailed logging makes it easy to find the source of the problem.
[Magisk] spawnmhsbc:
I find a solution that is disable Google play services , but it doesn't work

---------- Post added at 11:11 AM ---------- Previous post was at 11:10 AM ----------

Thank your sharing
[Magisk] samosaara:
Sony Xperia T2 Ultra Dual (D5322) Bootloop

I almost always feel bad for posting bug reports, because 90% of the time is me doing something wrong. I hope this isn't the case.

My environment is: this Stock, Brazilian ROM, kernel 19.4.A.0.182, lollipop 5.1.1, with (the v2 of) this patch, alongside this recovery (patched to be compatible with the dual version of the t2 ultra)

I'm not being able to flash into my (kinda old, originally android 4.4) Sony Xperia T2 Ultra Dual (D5322) I get a boot loop in every way I attempt it. I'll try to list everything I tried.

1. Custom recovery (TWRP) flashing

The stable version fails as expected (I guess), fails instantly without doing anything and asks me to go get (https://github.com/AdrianDC/android_boot_bridge). The beta seems to be able to install without the bridge, but the result is the same as 1.1.

1..1 Custom recovery (TWRP) flashing - With sony boot bridge

So the result of this attempt will be the same in many others. As asked, I gone and got the bridge, put magisk 15.2 (I tried this with both this beta and stable) inside the bridge's install folder and renamed it to install.zip as stated in instructions, and installation to works just fine. (recovery logs are here <--).

RESULT: When I try to restart it seems the device is in a very very bad boot loop, my recovery is gone, (doesn't show the led waiting for volume press, and doesn't work if I press regardless). I can't even log cat, doesn't get that far, it loads the sony logo, does that minor change in brightness, and some seconds before it would usually show the android logo, it resets, hence and repeat.

2. Generating the .img from magisk manager

So, first of all I didn't have my .img file because old sony, hence .ftf, so firstly I tried to generate with my current (dual recovery) boot.img, seems to work, when I flash it with fastboot, same as result 1.1.

I also tried to generate with the, renamed to boot.img, kernel.elf that I extracted from the kernel.sin that I extracted from my .ftf stock image. But then the magisk manager img generator locks me off saying it needs the boot bridge too but like... How am I even supposed to...? I get it that the manager generally uses the stable zip, I tried select the beta in the configurations, didn't help.

3. Old version

I'll just add it here for the sake of completeness but high change of being pointless. I tried version 14, and this patched 12 they don't do anything, don't break my recovery, don't boot loop, but neither get recognized by (the latest) MagiskManager, not even old version, just nothing. I also tried to boot 15 over these, but no help there..

This is all I remember trying, if I remember or try something else I'll try and update this. Would love to invest more time into helping solving this possible bug, if it ends up being one. I bet that an actual boot log would help a lot more but, AFAIK the kernel only logs to /tmp that gets flushed on reset, and I wasn't able to get any log, and magisk not even gets to generate /data/adb/magisk_debug.log. Will be here in case there is the need of any more logs or testing. Thanks.
[Magisk] Krendelrus:
Running Magisk v15.1 right now on Mi 6. Magisk updates just fine to v15.2, but after reboot my phone is stuck in TWRP running openrecovery script wiping data reboot after reboot. Only full wipe (w/internal storage) can stop it from looping.
[Magisk] satori83:
I have tried updating numerous times on my Pixel XL running RR rom with 7.1.2 but magisk never gets detected and the newer managers dont show any setting options on the left. I was using 14.3 just fine and want to downgrade now but all the beta links are gone!!! Did they move or does anyone have a copy? Please..
[Magisk] Didgeridoohan:
The /data/magisk symlink is just there for some backwards compatibility. No need to delete, and it will temporarily be removed when MagiskHide does it's thing.

---------- Post added at 06:42 ---------- Previous post was at 06:37 ----------

Nope... It's a big log and I have not sat down at a computer since you posted that. I hate reading logs on my phone...

Besides, I'm not the best at reading logs, so hopefully someone who actually knows what they're talking about will see it.
[Magisk] spawnmhsbc:
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------

Junior Member10 posts Thanks: 2

I give up updating Jan. Security patches.

I had already used magisk to uninstall stock image,As per ota installation tips of magisk, I guess currently slot A has stock boot images, slot B has pactched boot image, if I directly reboot, will lost root obviouslly, may be it Will bootloop because of different boot images in slot A and B .

Can I use magisk manager reinstall magisk v15.2, that Will keep root?
[Magisk] Didgeridoohan:
I took a quick look at the recovery log in 1.1 and the only thing that I think might be an issue is in the bootbridge part of the flash:

dd: writing '/dev/block/platform/msm_sdcc.1/by-name/boot': No space left on device

I'd ask in the Boot Bridge thread about that.

Edit: might of course also be that your device simply isn't compatible at the moment...
[Magisk] RamHa:
Can someone pls clarify for me, what is meaning of that marked on my scrsht N950F latest Magisk flashed from TWRP v15.2, and should be checked? tnx: :fingers-crossed:
[Magisk] RamHa:
just reflash Magisk 15.2 zip :fingers-crossed: from TWRP, happens 2 me 2 ;)
[Magisk] mohdnurr:
[YOUTUBE]https://www.youtube.com/JZIL6_g1Fes[/YOUTUBE]

https://youtu.be/JZIL6_g1Fes

What is issue of this situation?

Look ok after install

Lost magisk after using module or root apps.

Reinstall and work fine until using module/root apps.

Please help.

Oppo F1 plus. Marshmallow
[Magisk] jenslody:
I didn't read the logs, but this is normal when writing back the patched boot-image with dd on some devices. It writes the image concatenated with /dev/zero to make sure, that nothing of the former boot image remains in the partittion. It simply writes zeroes until the boot device is full and stopsbwigh this error message.
[Magisk] rk2612:
Untried / untested but a possible solution ...

1. Downgrade your bootloader by flashing firmware from OOS4.0.1.

(Refer https://xdaforums.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015 for download link)

2. Use the weakness in that bootloader with fastboot oem command to disable and then enable dm-verity.

3. Then upgrade your firmware again.

...might be safer not to boot into system while you're doing this and boot into recovery instead.

Might work. No guarantees and no responsibility if it doesn't. :silly:
[Magisk] sandaljrpit:
Not success :(
[Magisk] Maxiride:
On the official instruction to install magisk it is explained this path:

I have a Oneplus 3 everything stock, the stock recovery has an "install from internal storage" option, can I install Magisk this way without unlocking the bootloader and flashing a custom recovery like TWRP?

Apart from the installation process is there any difference in having plain Magisk or Magisk Manager?
[Magisk] mrror:
Root and Manager unstability

Since the recent updates I've been able to mitigate my previous problem (FC's on app launch) but Magisk Root and Manager still are somewhat unstable.

Basically, there are still Manager force closes, plus root apps (Titanium Backup, Total Commander, Xposed Installer, Greenify) are often "forgotten" so I always have to grant them root access (which sometimes is denied, or if it works often leads to Manager fc).

Here are two logs with all the cases I've been able to reproduce, but the usual pattern is:

- I open root app (ie Titanium Backup)

- App asks for root access

- After allowing it, Magisk Manager force closes

- On next app launch, root access is granted

I'm on a Moto G 2015 with latest stock (6.0.1).

Thanks for looking into it!
[Magisk] jenslody:
Fetch a logcat as I describe in my post.

---------- Post added at 04:09 PM ---------- Previous post was at 04:02 PM ----------

Magisk roots your device, provides the possibi

ity to change your device systemlessly and can hide this changes from other apps.

MagiskManager manages root-access, the hide list and can patch boot images, if the system is not already rooted.
[Magisk] S-trace:
Bugreport:

There is a minor bug in Magisk-v15.2.zip installer - it installs to wrong boot partition.

My device have support for dualboot: there is main (active) OS on the mmcblk0 and another (inactive) OS on the mmcblk1, both mmcblk devices is partitioned with GPT in almost same way. Linux kernel maps desired SDCC host to mmcblk0 when booting OS, and so currently booted OS is always using mmcblk0 device.

Recently I tried to install Magisk and found that installer selects wrong partition to install.

Install log: http://paste.ubuntu.com/26326247/

Interesting part is:

- Found boot image: /dev/block/mmcblk1p21

This is wrong partition, it should be /dev/block/mmcblk0p21 - so, Magisk installed its files not into current OS, but into another OS, which was not active in time of installation.

If I remove SD card with inactive OS before installing Magisk - it will install its files into /dev/block/mmcblk0p21, which is correct. But it is not very handy to remove SD card every time and to tell every user of this device about this trick.

Could You fix it?

Thank You.
[Magisk] sandaljrpit:
Sorry , im noob

https://drive.google.com/file/d/1jv2rUyNgGFmA0iKpa5Ma2GggEE1p1XNl/view?usp=drivesdk

https://drive.google.com/file/d/1Ju4gxM9MB4u4E7H8k2YH1Rj9aGFJC3Vg/view?usp=drivesdk
[Magisk] samosaara:
Yeah, it did seem harmless, I asked in boot bridge's forum just in case, but can it be the case that magisk simply isn't compatible with my device? What to do then?
[Magisk] barramas:
hello my friends.i am the happy owner of a huawei mate 10 pro.but magisk root is not available.

possible to see working on it????

very thanks to dev for your very hard work
[Magisk] jenslody:
Are you sure tcash wallet is still in magiskhide list, when you start it ?

In your magisk-log I see you magiskhide gets stopped and restarted and then tcash wallet gets removed from the hidelist.

And in the other log, I don't see and mention of magiskhide, but I see that tcash wallet sees "/sbin/su".
[Magisk] Bad_Calzoncillos:
Hi. I'm using Omni ROM 8.1 2017-31-12 for OnePlus 3T, and I'm having an unusual error. Apps keep asking me for root permission, even after repeatedly agreeing, they keep asking. The two apps that didn't have this issue (Nova and Cerberus) if I go to the Superuser tab and try to disable them, Magisk Manager crashes.

I've attatched a logcat and also contacted the rom developer. Thanks!
[Magisk] sandaljrpit:
Im try again..

https://drive.google.com/file/d/1lyD5zFqMHCIDadsc-aNndXxOE8H48NqH/view?usp=drivesdk
[Magisk] nightraving:
I'm running into a rather annoying problem when trying to install the Stereo Sound Mod for my One Plus 5t. Stock ROM and kernel. When attempting to flash the zip via magisk, it tells me that 'Magisk is not activated' and then proceeds to abort/fail the process. Ran into the same results when trying to flash via twrp. In fact, I've ran into this error a number of times - like when trying to install xposed via magisk manager. I'm not sure what the problem is since magisk is clearly installed and I'm properly rooted. I checked the data partition and the magisk.img file is there. Any ideas? I've attached the log
[Magisk] palmuse:
I am going nuts over an error in Magisk Manager. I have v5.5.3 and Magisk v15.2.

It says "Invalid Update Channel" on main screen so I cannot access any modules on the repo. I have tried changing to beta, stable and custom paths.

I also just uninstalled and reinstalled Magisk and the Manager. After my second reboot the repo showed, I installed one module and lost it after reboot.

I have also tried turning off any blockers and reverting hosts. Not doing it.

Anyone else have this an found a solution? I can get to my old modules in my internal card, but I know some are old and other new ones look appealing. :D

Thx
[Magisk] jerrygoh389:
Can someone help and tell me what is going on my device.. Attached log file thanks
[Magisk] nightraving:
You might want to explain the problem. Oh and what device you have. Oh and what ROM you have too. Come on man, the people in here aren't mind readers...
[Magisk] mwilky:
[MENTION=4470081]topjohnwu[/MENTION]

Latest sepolicy seems to block dex2oat accessing data/dalvik-cache/arm & data/dalvik-cache/arm64 folders.

I have tried:

"allow dex2oat dalvikcache_data_file file { write read execute }" \

"allow dex2oat dalvikcache_data_file dir { write read execute }" \

"allow dex2oat dalvikcache_data_file dir create_dir_perms" \

"allow dex2oat dalvikcache_data_file file create_file_perms" and a few others to no avail, you have any ideas?
[Magisk] jenslody:
It's the "/default.prop".

You have to change "ro.secure" to "1" and "ro.debuggable" to "0".

You can check if it works by mounting the rootfs readwrite:

mount -o remount.rw /

after running "su" (and granting root rights) inside a terminal or inside "adb shell".

The edit "/default.prop" and change the two values accordingly.

As I wrote before this will not revive a reboot, because default.prop is copied from boot-image on every boot.

So either you have to edit it inside the boot image.

It's possible with Magisk, but doing it manually is a little bit too much for a newbie I think.

Several solutions come into my mind:

a module that does it inside boot-image when flashed (should not be too hard to create),

a shell-script that patches "/default.prop" on every boot, a little bit easier than a module,

a simple script, that replaces "/default.prop" with a working one on boot (easiest).
[Magisk] samosaara:
Hey everyone, I've got it, I needed to patch sony RIC, it was the one causing the issue it seems, worked flawlessly after I applied this patch alongside X2's twrp recovery, praised be the unified kernel! I really think this should be added to the install instructions!

I didn't even bother because I want to use xposed, but I bet I'm not getting nowhere near past safety net without RIC
[Magisk] sandaljrpit:
thanks a lot brother, this helps me a lot. :angel:
[Magisk] JaymzTA:
I am having the same problem as Bad_Calzoncillos.

I'm on OmniRom 8.1 2017-31-12 for the OnePlus 3T. Whenever I grant an app root access, Magisk doesn't remember and I have to Grant access over and over. For some reason, Titanium Backup is the only app to hang onto root access. So far Greenify and BetterBatteryStats ask Everytime I open them. Anyone know what's going on?

Thanks in advance.

EDIT: Using latest Magisk Manager and Magisk versions.
[Magisk] mobileman88:
You might want to stop and delete all data from the Magisk manager app
[Magisk] JaymzTA:
Thanks for replying. I've already done that. I've also uninstalled Magisk Manager and Magisk, then reinstalled. Same issue afterwards.
[Magisk] arunsai123:
Magisk asks for permission grant again and again.

It doesn't remember root permission and asks again and again.

attached logs here. magisk 14.5 works without any problems.

It says error opening database.

Magisk version: 15.2

ROM: 8.1 AOSCP

DEVICE: redmi note 4 sd

data formatted in f2fs
[Magisk] DiamondJohn:
I may of got to the bottom of all this seemingly "random" behavior :o

Last night my phone went into a melt down and fell to pieces with all sorts of issues :crying:. I tracked it down to a single badly corrupt file (at least the first processes would complain about) in the data partition, which could not be touched; Even TWRP failed in creating a backup! :mad:. This to me signified I had a corruption in my data file system. Long story short, I repaired my data partition, and restored my previous nandroid. This backup had the old Magisk in it, so I went through the whole upgrade process of Magisk, and low and behold, it all went smoothly and worked first time:rolleyes:

Sorry for wasting anyone's time with my hardware issue.:o
[Magisk] Regys:
Hi,

Which SafetyNet to install with 15.2 ?
[Magisk] Necma:
Hi, I have Xiaomi Redmi 4x with last miui europe rom and the last magisk update and Adaway and FastGPS are not working...

There is only a black screen and they don't ask root permission..

On xiaomi.eu they stated that it is a magisk problem... I dunno...
[Magisk] kerpert:
Paypass (Intesa bank app) recognise the root even hided Magisk and even the phone passes the SafetyNet check.
[Magisk] antariksh:
Magisk v15.2 is causing some major issues. The ROM is getting stuck on Lockscreen itself after few reboots and then device reboots. You can't do anything. Happened to two of my devices running Lineage OS based ROMs. The same ROM is working fine without Magisk.

Is [MENTION=4470081]topjohnwu[/MENTION] aware of this issue?

Update: Solved. sorry
[Magisk] Didgeridoohan:
Logs or it didn't happen... And Adaway has been discussed quite a lot recently. Search through the thread and the rest of the Magisk forum and I'm sure you'll find something.

Not quite sure from your post, but have you hidden the Manager as well as added the app in question to the Hide list? Hiding the Manager is a somewhat new feature that solves a lot of issues with apps detecting root. Go to the Manager settings and you'll find an option for it there. You might also have to clear data for the app since some apps remember if you're rooted.

Logs or it didn't happen...
[Magisk] khaytsus:
Okay....... I'm apparently a tard. I have downloaded the last four factory images, none of them have a dtbo.img in them. What am I missing? I'm on a Pixel XL, Dec build, with Magisk 5.4.3 and trying to prepare for any problems that I've been reading about to update to Jan but I'm just clearly missing something. I'm looking in the main zip contents as well as the image-build.zip contents within it, of course. Not seeing it anywhere
[Magisk] kerpert:
Of course the app was also with the box checked in the hide list but I didn't remember to had clear its data.

So I did this right now, followed by a phone reboot and by set Magisk to deny every root request, before open the app, but this not work.
[Magisk] Luniz2k1:
You need to hide the Magisk Manager
[Magisk] jenslody:
But did you also hide the MagiskManager itself.

In the settings you can hide itself by repackaging it with a random package name.