yashsingh1/xdaforums huggingface dataset:
[Magisk] BeeWall:
Reinstalling fixed. Probably should've thought to try that :rolleyes:

Also the issue was a single file, not the whole folder.
[Magisk] DodoGTA:
Rename the boot image to "boot.img" (without quotes) and tar it again
[Magisk] Didgeridoohan:
From a quick test it looks like that app merely looks for the Magisk Manager. Hide it... There's an option for that in the Manager settings.
[Magisk] targitay13:
It was almost obvious ...

But I thought that since "patched_boot.img" is flashing normally, then any other name will do!

I even tried "boot.img" at the very beginning, but apparently on an unsigned image, and it also gave me an error.

Renamed "new-boot-signed.img" to "boot.img", tared it - and voila!

Successfully flashed, and Magisk Manager is showing "Installed Version: v15.2"

But when started, MM is asking for update Magisk to v15.2 (direct install doing nothing)

So, here is boot.img for Samsung XCover3 (SM-G388F) Android 5.1.1, patched with Magisk 15.2, to flash with Odin if anyone needed in future

[MENTION=6429309]DodoGTA[/MENTION] thank you very much for help!
[Magisk] tys0n:
Did you rename it to boot.img before taring it?

That's what Odin expects to be able to know which partition to flash.
[Magisk] Veid71:
i read through the logs and i didnt see anything useful in them but ive attached them the only thing i saw in the flashing log was that usb-OTG didnt mount but it never has for some reason (although Magisk hasnt worked for me for awhile anyway so i guess that could be it?) also when i flash the bundle in twrp it doesnt install the manager at all
[Magisk] Didgeridoohan:
I've seen your logs, but have unfortunately nothing you add... There's something messed up about your setup (obviously), but it's hard to figure out what.

By this point I'd consider a complete wipe and fresh flash of your device to be a valid option...

Logs are always good, and [MENTION=6556047]Veid71[/MENTION] have actually posted logs on several occasions before. It's a long running issue...
[Magisk] Veid71:
that's what i was thinking but im not sure what, on previous versions ive flashed to stock a few times to try and get it working but i havent done it on this version yet i suppose ill try it, is this a common issue for pixel XL's or am i the only one with it?
[Magisk] targitay13:
Thank you. Renaming to "boot.img" has made the trick!
[Magisk] Didgeridoohan:
Did you do a complete wipe and a clean flash those times?

I have no idea about Pixel devices at all, but I don't think I've seen anyone else with your specific issue.
[Magisk] Veid71:
i didnt do a wipe but i flashed the stock firmware from googles website so i assumed that wiped everything cuz none of my settings or folders are there afterwards, i think magisk or Super SU might be keeping something in my root or system side of my device but that would get cleared when i flash the stock right? ive noticed after i run the uninstaller magiskmanager folder stays and on the older versions where i could download modules they would show up again in my MM folder even after an uninstall (which they shouldnt be there right?)
[Magisk] nightraving:
When I try to install the xposed module via magisk manager I run into the following error:

But Magisk is clearly installed and working correctly. I pass root checks and am able to grant SU to whichever app I want. So I'm struggling to understand what the problem is. The same also happens when I try to flash systemless xposed via twrp. Any ideas?

Using a One Plus 5t on 7.1.1 stock ROM and stock kernel

This is the logwhen using 'magisk' as search parameters in catlog. Don't know if it's at all useful though
[Magisk] wtfkilla01:
yeah i know this main banking app need magisk hide too; but this wont work look;
[Magisk] Shtiff1:
Magisk hide is good, BUT hide the MANAGER also
[Magisk] SonOfTheRain:
Hello,

I had issues with bootloops etc so I did following to get Magisk work:

1. Reflashed stock rom via Firmware Finder to my Mate9. Version is MHA-L29C432B198.

2. Unlocked bootloader, hard reset automatically and installed twrp-3.1-hi3660-c432b182.img. Works ok in TWRP.

3. Installed Magisk v14.5(1456).zip via TWRP, installed properly (I couldn't install v15.1 directly, when it gave error, developer options stopped to work, I could not restore from backups and Huawei Backup app crashed and only reflash the rom helped). However SafetyNet fails.

4. From Magisk Manager I updated to v15.1 and SafetyNet fails. V15.2 fails too.

Can anyone help me how to SafetyNet get passed? Despite I do MagiskHide, some apps still say to me that my phone is rooted. My log is in attachment

Thanks
[Magisk] wai10691:
I am on OxygenOS 5.0.1 and with the latest Magisk 15.2.

Everytime when I reboot I found that Magisk Hide got reset. Need to tick the app that need to hide root again.

Anyone idea on how to fix this? Anything I can provide (log) to help on debug?

Edit: found this in the log

01-05 18:32:39.181 469 8198 I Magisk : hide_list add: [my.com.maybank2u.m2umobile]

01-05 18:32:39.277 469 8198 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

01-05 18:37:35.260 469 936 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=10233 ns=mnt:[4026534424])

01-05 18:38:24.649 469 936 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=10507 ns=mnt:[4026534378])

01-05 19:03:32.394 469 14851 I Magisk : hide_list add: [com.First]

01-05 19:03:32.493 469 14851 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

01-05 19:03:34.990 469 14854 I Magisk : hide_list add: [com.citibank.CitibankMY]

01-05 19:03:35.095 469 14854 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
[Magisk] jenslody:
If magiskhide does not work properly safetynet can not pass.

Did you try it with disabled modules or in core-only mode.

On stock samsung there have been selinux issues, that have been fixed in 15.2, there might be a similar issue on huawei, too.
[Magisk] Shred00:
Unable to repack boot image!

Using Magisk Manager 5.5.3 (86) I am unable to install Magisk v15.2. I have installed many previous versions of both the manager and Magisk but v15.2 is failing with:

- Device platform: arm
- Extracting files
- Use boot image: /dev/block/mmcblk0p18
sh: <stdin>[466]: /data/user_de/0/com.topjohnwu.magisk/install/magiskboot: not found
grep: /etc/*fstab*: No such file or directory
- Mounting /system, /vendor
boot_patch.sh[80]: ./magiskinit: not found
- Unpacking boot image
boot_patch.sh[89]: ./magiskboot: not found
boot_patch.sh[119]: ./magiskboot: not found
boot_patch.sh[150]: ./magiskboot: not found
boot_patch.sh[165]: ./magiskboot: not found
boot_patch.sh[170]: ./magiskboot: not found
boot_patch.sh[177]: ./magiskboot: not found
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
Failed!
! Installation failed

Any ideas how I should resolve this?
[Magisk] Andrean123:
Trying to install v15.2 but when I rebooted it says magisk isn't installed.

I attached recovery log when installing magisk.

Redmi 4 Prime running MIUI 9 7.12.28 Android 6.0.1.

Tried patch boot img manually from magisk manager and flash patched img from twrp, still same result.

Any solution?
[Magisk] korom42:
More logs for 15.2 with different kernels (all ended in boot-loop)

Patched with this tool (unofficial build with Oreo support, It makes the kernel rootable + disables "force-encrypt", "SONY RIC" and "dm-verity" for xperia kernel + patches drm), tried different settings each time

More info about how the tool works here and here
[Magisk] Mondor1979:
Can not install magisk (any version) on honor 9 oreo latest 333 or 321, doesn't matter.
[Magisk] Sebastl:
Specs:

Process so far:

Searching / Debugging so far:

Long story short: Seems like those F*****S ship a kernel without loop support.

PS: Sorry for thinking of TWRP SElinux problems first - i was mislead by the TWRP "SElinux fully supported". It was running in permissive anyway...

Took me half a day - maybe the approach helps someone ;)

Edit: Thx [MENTION=8010004]guest4711[/MENTION] for the hint. And [MENTION=6220053]Nephiel[/MENTION] ;) But that module targets a different problem, thats why i mentioned No F2FS in the specs. And otherwise it would be a Catch22 ;)

Edit2: Doogee S60, BV8000 and Ulefone Armor2 all seem to have the same(kernel)problem. Very similar phones, but different "producers". Probably the same factory / developer selling "unique" products.....
[Magisk] dr4go:
To be honest... I'm surprised that this works with older magisks. The drmfix-system-mode.zip you need to flash, already modifies system(/vendor/lib) and oasisfeng mentioned in the releaselog: say Y to every option. That's what I did with my X Performance as well... My girlfriend soon gets the XZ so that I can test a bit more... I may be wrong, but I don't think that the bootloop is magisk related / msgisk's fault...
[Magisk] guest4711:
In magisk repo there is a module called "F2FS Loopback Bug Workaround" by [MENTION=5228676]VR25[/MENTION] which should be flashed using TWRP. ("Magisk functionality without a custom kernel. Install from TWRP and forget"). Perhaps you should try it:...
[Magisk] Nephiel:
I have what seems to be the same problem, reported here.

Doogee S60 7.0 / Kernel 4.4.15 / No F2FS / Allow OEM Unlocking / Bootloader Unlocked
Fresh Stock Rom / Fresh TWRP 3.1.1 / Fresh Magisk 15.2 / Magisk Manager 5.5.3 (86)

Thank you! I've spent over 3 days with this issue. Very much appreciated.

Thank you! Trying the F2FS test described in this post, and it fails:

S60:/ # mkdir /data/f2fs_test 2>/dev/null
S60:/ # make_ext4fs -l 8M /data/f2fs_test.img
Creating filesystem with parameters:
Size: 8388608
Block size: 4096
Blocks per group: 32768
Inodes per group: 512
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 2048
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/512 inodes and 1070/2048 blocks
S60:/ # mount /data/f2fs_test.img /data/f2fs_test
mount: losetup failed 1

Now I'm going to flash everything back to stock, then try the F2FS workaround module.
[Magisk] guest4711:
I don't think you need to go back to stock. Go into recovery, flash the workaround, flash magisk... That should be all.
[Magisk] Nephiel:
Maybe, but I've spent a few days messing with this device, so there's no harm in starting with a clean slate.

Anyway, I tried it and doesn't work (yet).
[Magisk] madbat99:
Yeah, don't think your issue is f2fs loopback bug. That usually gives magisk_merge.img failed to mount error. Not permission failed.
[Magisk] Nephiel:
That's precisely the kind of errors I'm getting when trying to install modules:

! /data/adb/magisk_merge.img mount failed...

The permission denied error is in Magisk log:

mount /dev/block/loop0->/sbin/.core/img failed with 13: Permission denied

I don't think the issue has anything to do with F2FS in my case, but the workaround is worth a try ;)
[Magisk] Veid71:
hey so i just updated my phone to 8.1 on the January update via OTA and flashed the newest TWRP (not sure if this was the problem or not i was using 3.1.1 before) but for whatever reason 3.2.1 refused to work on the XL for 7.1.2 for me atleast not sure about others, it couldnt decrypt my phone even though i didnt have a password on not sure what that was about, but at any rate i was looking at the log for installing and it looks like the difference was that now it can mount the usb-OTG where as on 7.1.2 it couldnt do that but ive posted the logs between the new one and the old one so you can compare them and look at them for yourself if youd like, i wish i could have gotten it working 7.1.2 for xposed but i guess it is what it is hopefully you guys can figure it out so no one else has this issue but thanks for all your support ^_^ [MENTION=4470081]topjohnwu[/MENTION] [MENTION=4403217]Pkt_Lnt[/MENTION]
[Magisk] bunklung:
restore image no workie DTBO; break sideload full OTA Pixel 2

This did not work for me. I actually came across this issue in a different way. I updated Magisk via the app at some point and saw this scary message after a reboot. I didn't think much of it, but when I went to flash the factory OTA image (January), it could not validate the image. The only way I could get this to sideload the full OTA was to restore the old dtbo partition and boot.

Preserve AVB 2.0/dm-verity are already checked on my device, so restoring the image and reinstall Magisk does not fix the issue!

Fast forward to a few days ago.... I finally got the OTA to stick, and installed new 15.2 Magisk image and made sure that both Preserve AVB 2.0/dm-verity are checked. By default they are (for me?). The phone was working great for a few days, until Magisk decided to *automatically* patch dtbo without *ANY* prompt from me. I saw the message and it told me to reboot. I did and now I have the scary message again while both Preserve AVB 2.0/dm-verity are checked! I followed the instructions again and no dice.

1. Why does it patch dtbo when I have Preserve AVB 2.0/dm-verity both checked? This patching is randomly without interaction.

2. Why does Preserve AVB 2.0/dm-verity have no function?

3. Why does it not restore dtbo when I select restore images? It certainly restores boot.

4. Patching dtbo breaks sideloading FULL OTA updates, FYI. I don't want to generalize for all users, but I like being able to sideload full OTA updates each month without any jockeying.

So I guess this is a bug? Pixel 2 January 15.2 Magisk. Downloading the full factory image to restore dtbo, although it's not clear if this is going to stick as Magisk might automatically patch dtbo again?

Big thanks to all the devs on Magisk as a whole! I love it. Thank you Thank you Thank YOU ALL!
[Magisk] kacper111:
I'm seeing the same issue where Magisk is deciding to patch dtbo on its own even when preserve AVB 2.0/dm-verity is checked. This only started happening in the last two days.
[Magisk] samosaara:
Bro, you just solved my problem, thanks :D It was sony RIC all along.
[Magisk] rriegner:
I'm having the same issue on 15.2, though mine is remembering two root apps and forgetting the rest. Came here looking for answers, but it seems it hasn't been found yet. I can provide a log if helpful.
[Magisk] bunklung:
I tried a few things and it's actually pretty consistent. I have reflashed dtbo in fastboot and without fail, Magisk will patch dtbo on every single boot regardless of the checkbox, "preserve AVB 2.0/dm-verity". I figured maybe the option was inverted. I also toggled systemless hosts within options to see if that had an effect, nope.

Just to be clear, the scary boot warning is not a concern for me. The issue is when I have to update my phone to knew security updates. I run stock, so having to redownload a 1.2GB image to get a tiny dtbo file is not ideal. I think it adds a huge complexity layer for the average stock-rooter. I presume many user will do a full factory reset when they can't flash the full OTA which is a bad day in my book.

Would you like logs or has this bug been confirmed?
[Magisk] mastercko:
Display Issues on Nexus 6P

Hi all,

I am having a very annoying problem with the display on my Nexus 6P on Magisk 15.2 and I'm not sure what the best reporting method is. The specific symptoms are:

When booting to system after installation (via TWRP 3.2.1-0), the phone works OK for a few hours

After a few hours, for some reason the phone goes into this weird state with the display:

If the phone was asleep when this state change occurs, the phone's screen won't turn on when I press the power button (i.e. it remains off)

If the screen happens to be on when this change occurs (or it turns on automatically when I pick up the phone due to "Lift to check" being turned on), the screen is in a weird state where only half of it is on. I believe it is the left half that is on and right half is off. Touch response is very erratic, sometimes it works and sometimes it doesn't.

Other than these specific display issues, the phone seems to be running normally in the background. Specifically to my case, I have observed it still doing the following while in this state:

Ringing an alarm

Playing music over Bluetooth

Receiving a phone call

I can only get out of this state by hard resetting the phone (long press power button).

I haven't figured out a way to repro this issue other than to wait. Is this something that anyone else has seen before? It has been an issue that I have experienced on this phone since 14.6 and onwards, so I always have to roll back to 14.5 if I want to run Magisk, but I haven't seen anyone else mention it when searching, so maybe it's something specific with my device?

I have attached logcats that I captured right after booting while the phone was still running before I went to sleep ("normal") then after the screen issue occurred ("unstable") after I woke up. It's hard for me to be capturing the logs of the exact moment that the issue occurs (due to its nature and the fact that I'm not constantly looking at the phone), but hopefully the logcats cover enough that someone can make something of it.

If you need the magisk_debug.log file, I can get it when the phone next has the issue, but I forgot to grab it before I uninstalled and reinstalled magisk. Let me know if you need it or something else. Thanks in advance!
[Magisk] :
Got this log from the application.
[Magisk] showlyshah:
A weired problem on my pixel 2 xl.. i am using flash kernel 2.8, with jan 5 security update.

I installed 15.2 magisk from twrp. Everything was fine.. rebooted.. installed modules.. rebooted ( no dtbo warnings) and all modules are working..

Soon after some restart.. suddenly magisk showed notification - dtbo patched.. please reboot... So i rebooted.. ( now dtbo warning pop up) and when i checked modules.. it just shows.. modules will be updated after reboot.!!

I rebooted several times.. still dtbo warning and modules always show same " will be updated after reboot" message..

What could be wrong?
[Magisk] Badger50:
Nothing is technically wrong. The magisk manager app is patching the dtbo.img, thus giving the message at boot up. The Dev knows. There is a modified mm app out there that takes care of the issue. It's really nothing to worry about though.
[Magisk] showlyshah:
I know.. but why dont it do the same at first time after i rebooted??

Also after patching.. all modules uninstall button got greyed out.. so no unistall option..

Btw.. i fixed it.. clear data of magisk.. but that didn't remove modules or changed the greyed out uninstall option.. then i reinstalled all modules ( which of course will remove previous versions and did fresh install.. rebooted and now modules working..

Think this is a bug in magisk.
[Magisk] Badger50:
I didn't have any of the modules greyed out problems, just the patching after 3-4 reboots. Other than that, it's working fine on my P2XL.
[Magisk] gametimebrizzle:
BOOT LOOP 15.1 -> 15.2

HTC 10 - Android N (7.0) - LeeDroid - ElementalX

Had to restore boot img with pre Magisk v15.0, notably v14.3 worked for me. Glancing at logs, fstab is still causing issues.

Here's some logs

- Current Magisk (14.3) log (with errors) ** this is the only 2018 log that is going to pertain to v14.3

- Magisk v15.2 install logs (showing success, but fstab issues)

Edit:I added more logs than I prob needed to, but if I didn't upload the correct logs, please let me know

Edit#2: I'll leave it for reference, but this is fixed. I redownload latest uninstaller and latest beta and ran checksum (on git). Good files.

Then used Flashify to batch the process - hoping to avoid the loop that was happening during the reinstall of Magisk (between boots during the upgrade transition)

"Batch"

- flash uninstall zip

- backup boot image (just in case)

- flash lastest beta build

Result

- phone is running fine Magisk 15.2
[Magisk] manan001:
Unable to open any modules after installing 15.2 on mia1 android oreo 8.0
[Magisk] cooke6:
Exact same issue here. See thread below for some additional info. Are you using f.lux or some other display mod? May or may not be related cuz I'm pretty sure I've had it happen with and without it installed.

https://xdaforums.com/nexus-6p/help/crashing-t3727651
[Magisk] ludditefornow:
Xiaomi MIA1

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3. on Xiaomi MIA1.

1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.

2. I unlocked the bootloader

3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.

4. I followed this guide https://github.com/topjohnwu/Magisk/...tallation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.

5. When I download the second december OTA update I get a failure to install error at step 2 of 2.

Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored? There is no log file at /data/adb/magisk_debug.log and there is actually no ADB folder either.
[Magisk] lalitjoshi06:
Using infinix x603 with magisk 15.2.

Magisk root working but module not wirking.

4.4.15 kernel with mt6757 chip.

Loopback command is disabled in kernel.

Data in f2fs cache in also f2fs. No support for ext 4 cache partation.

If i format it to ext4 always bootloop. Its Only booted with f2fs.

Is there any way to use module in current situation.
[Magisk] madbat99:
There is a module that is an f2fs loopback bug workaround. Needs to be flashed in recovery. It's in the repo. May help.

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875/post71554247

Just noticed cache is also f2fs, so that module won't help, sorry.
[Magisk] abdelrahmannagi:
HI, [MENTION=4470081]topjohnwu[/MENTION]

I flash magsik v15.2 on my s5

but when I boot there is no magsik manager app although it has succefully installed in recovery

---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------

HI, [MENTION=4470081]topjohnwu[/MENTION]

I flash magsik v15.2 on my s5

but when I boot there is no magsik manager app although it has successfully installed in recovery
[Magisk] tag68:
Please read the problem and the description of the module before posting a solution that will not help in any way.

You recommended f2fs workaround module because cache is f2fs. The f2fs workaround module does move Magisk to the ext4-formatted cache partition, if data is f2fs. But cache in this case is f2fs ...
[Magisk] madbat99:
Just noticed that cache was f2fs. But I did say MAY help.
[Magisk] JustinChase:
I have reported the same thing, running nougat on HTC U11.

I reverted to version 14.5 and it's working again.

Sent from my phone, forgive any spelling errors
[Magisk] coldplug:
Thanks. Good to know its a magisk bug and not me f'ed up somewhere.
[Magisk] mastercko:
Hi cooke6,

Thanks for pointing me to that other thread, I thought I was the only one having this issue. I have had an update since posting my original message and I actually already added it to that thread, but I'll put it here, too:
[Magisk] Falseclock:
[MENTION=4470081]topjohnwu[/MENTION]

Device: HTC U11

Firmware: 2.33.401.10

OS: Oreo 8.0

System hangs on HTC logo
[Magisk] mwilky:
[MENTION=4470081]topjohnwu[/MENTION]

Next time you come around to playing with magiskpolicy, would it be possible to add some output to logcat? I.E when the "--live" phase begins, what policies we are patching, when it finishes? Would be useful for running script on boot.

Thanks a mil