yashsingh1/xdaforums huggingface dataset:
[Magisk] Madd_Maxx:
Hi guys!

My problem ...

I install Magisk. Open Magisk Manager and update to the latest version. Run Root FTP Server on device and provide root access. In Root FTP Server check box "System is RW mode".

Run program and go to PC. On PC run FlashFXP ftp client. Connect to device on ftp protocol. Go to /system/ and attempt to change the name build.prop to build.prop222.

FlashFXP on PC writes ---> "ERROR! Read-only files system. Cant delete/remove/rename."

Delete the Magisk through TWRP. Install SuperSU. I repeat all the same thing. Result ---> "Rename OK."

Why?

Tested on Android 7.1.2 (MIUIPro Dev 7.12.21 & RessurectionRemix 5.8.5)
[Magisk] flipmode_11:
# BUG REPORT # Magisk Manager v5.6.0 - v5.6.1 [Beta & Stable]

# BUG REPORT # Magisk Manager v5.6.0 - v5.6.1 [Beta & Stable]

ISSUE: Things are not behaving normally within the Manager. Select Magisk Hide to turn on side-menu. Click - back - Left Menu. Great Magisk Hide is there and it opens ok. Exit app by pressing Back or Home. Re-open Magisk Manager immediately. Left Menu - no Magisk Hide...? Open Settings, enable Check for Updates - back - exit. Open app and go to settings. Check for updates is now disabled again?

Magisk SU updated 15.3 to 15.4 to 15.6 to 16.0. No issues, but there are 3+ settings ALWAYS lost, and other settings not lost. Only some are lost, as even if you make 3-4 changes to settings, re-open and Hide and Updates are both back Off. I forget the 3rd/4th setting. No other apps having issues. Just the Manager app that was malfunctioning. Kernel version is fine - it is more recent that my Galaxy.

Has anyone else experienced an issue with some settings saving in the Manager?? (3 so far that do not save after app closure)

More than happy to donate again. Keep up the excellent work! :D

Cheers and

thank you!

(removed due to ScaredDevil's objection)

X96 Quad Core ("P212" model?) OS 6.0.1 w/ S905x & 1GB DDR3 RAM and 4GB eMMC storage. 16.0:MAGISKSU.

[MENTION=269498]scared[/MENTION]Devil666, What are you talking about? You don't encourage or want people to donate towards different projects on XDA? What do you mean "aware what this beta thread is for right." is that a question? and what is "Most of the issues"??? I am reporting

ONE BUG

. Have you actually read my post?

Why do you need to be rude?

This IS the "BETA" thread.

You do know BETA = testing and reporting issues?! (non-stable/final!)

Would you prefer people create a new topic for every issue and bug to flood the forums? Great idea!

I have crossed out any signs of appreciation to the dev for you.
[Magisk] Didgeridoohan:
I completely understand the objection being raised. You're using the donation as an incentive. That's not what it's supposed to be used for... It's a token of appreciation, nothing else.

About your bug report. I've been trying different things to reproduce, but can't... You're going to have to provide some logs. And since the Manager is somewhat separate from the Magisk release, the general support thread might be a better location.
[Magisk] SacredDeviL666:
Cleaned few posts and moved the last discussion to Magisk General troubleshooting thread where we have all the best troubleshooters including [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] dimmak:
How stupid of me, it worked. Thanks.
[Magisk] Tattvamasi:
OP5 pachted_image won't boot

Hi,

this is my first thread here and I'v been using Magisk flawless 'till now.

Phone: OnePlus 5, Android 8.0 OxygenOS 5.0.2

Since the latest update: OnePlus5Oxygen_23_OTA_029_all_1801292040_f50c278a6e154736 the pachted image won't boot.

I tried with Magisk 15 and now with 16.0 (1600).

I didn't find any solution on the net, maybe somebody here knows it.

kind regards,

Rob
[Magisk] Wolfcity:
As [MENTION=4667597]Didgeridoohan[/MENTION] used to say: Logs or it won't happen.;)

"Image won't boot" isn't enough information for someone to help you. Provide at least a recovery log and a magisk log. You can find how to do that here on XDA on several places.
[Magisk] Wolfcity:
Do you flash the patched boot.img after you have created it? If yes, have you tried to flash the magisk.zip directly through TWRP instead of patching the boot.img? If you do so you can grab a recovery log too, after flashing magisk go to Advanced->Copy log.
[Magisk] Hemuli:
Installation fails on Lenovo A7600-F with ported AIM OS v2.5. Recovery log with failed zip install as an attachment.

Is there any way to patch boot images with an older version of Magisk? I was able to patch boot image before Magisk 16. Now patching and flashing results in bootloop. The sad part is that the newly patched image overwrote the older one.
[Magisk] Sam Nakamura:
Same on my Lenovo a7 40 a3500-fl / mediatek, patching a boot image from within magisk manager was working fine since external patching was introduced, now after choosing the boot image and clicking "patch boot image" nothing happens, when I transfer the boot image to another device to patch it there the process passes without errors but the patched boot image is shrinked to 6kb total in size...

I'll provide logs later on as I just have no time now but anyway I think I read several reports of issues with MTK and magisk 16...
[Magisk] guest4711:
See https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75673627 and the related posts. AFAIK the new archive there could be helpful for you - it adresses a problem like that you are telling about...
[Magisk] Hemuli:
I can patch my boot images in Magisk Manager but they are shrinked to 6kB, too. Attached are logs when patching with Magisk Manager.
[Magisk] guest4711:
See the post related to https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75673627
[Magisk] Hemuli:
I tried to flash in TWRP but it resulted with a similar memory allocation error to the one in my previous post https://xdaforums.com/showpost.php?p=75704217&postcount=5395

Should I try extracting Magisk Manager apk and try patching with it?
[Magisk] guest4711:
Yes, it's worth a try.
[Magisk] Hemuli:
It still generates a 6 kB patched image.
[Magisk] guest4711:
If it still fails to patch your unpatched bootimage using the apk from https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75704217 then it would be a good idea to post your unpatched bootimage here so someone could analyze it.
[Magisk] Hemuli:
I presume you meant to link to https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75673627.

I attached the image I'm trying to patch.
[Magisk] Didgeridoohan:
Just to make sure that everyone is going about it the right way...

If you want to use the Manager to patch a boot image with the fixed test build, you need to first change the update channel to the correct url. Take a look here:

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75665040#post75665040
[Magisk] jenslody:
How did you try it. Via modules, "+" and chosing the zip-file ?
[Magisk] Hemuli:
Yeah I switched Manager to that channel and now the patched image works. Thanks.

Is this link the same as beta channel? I totally forgot about the channel switch in settings and seeing this dedicated beta thread I somehow imagined I would be on beta channel if I use the files attached to the OP here. Either I'm dumb or it would be worth to mention the switch in the OP. Or then I just don't know what "related posts" means. :silly:

No, install -> patch boot image file.
[Magisk] jenslody:
No, it's a special build by [MENTION=1813976]shakalaca[/MENTION] who found (and fixed) typos in the original sources.
[Magisk] Nosferatu.:
OnePlus 5T

Factory Rom Oreo (OxygenOS 5.0.3)

Magisk Hide doesn't show any applications area is blank since updated to v16. I fully uninstalled using the provided Magisk uninstaller including Magisk Manager. Even tried rolling back to 15.3 and still nothing shows. I completely wiped data in Magisk Manager as well to see if any residual.

Thoughts?

EDIT: My wife's OnePlus3 also on Oreo updated to v16 without issue. What got lost in the process on my OnePlus5T?
[Magisk] Didgeridoohan:
Could you grab and post a logcat when refreshing the Hide list (pulling down)? If possible, a screen recording of it would be really nice as well....

There's been a couple of reports of this (I've experienced it myself), but we've yet to figure out why.
[Magisk] Nosferatu.:
Sure I'll do it later today. So...for now, should I just re-install v16.0 and Magisk 5.6.1? Should I try and revert further back say 15.3 and an older Manager? Right now I have Magisk completely uninstalled.
[Magisk] Nosferatu.:
Logcat attached as is video...

Whether dark theme or light theme still happens so it has nothing to do with the black background causing failure.

[YOUTUBE]__becpWc_1w[/YOUTUBE]
[Magisk] Didgeridoohan:
Thank you. No idea if it'll help, but every little data point matters... :)

For those that have been affected by this, the issue has disappeared by itself after a short period of time. For me it was after letting the device sit overnight, so I couldn't continue troubleshooting. :p
[Magisk] Harshiv989:
Cannot patch boot image file.

Running MagiskManager version 5.6.1(105) on Samsung Sm-E700H with Android Lollipop 5.1.1. I download Magisk v16(1600) zip file from Manager. select patch boot image. then select the stock_boot.img that I copied from backup copy Magisk had made somewhere. image file option in settings is set to .img option.

patch logs:

Device platform: arm
- Extracting files
boot_patch.sh: ./util_functions.sh: boot_patch.sh: line 15: grep: Permission denied
./util_functions.sh: line 15: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 15: ps: Permission denied
boot_patch.sh: boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied
./util_functions.sh: line 16: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied
boot_patch.sh: line 75: chmod: Permission denied
boot_patch.sh: line 78: ./magiskinit: Permission denied
- Unpacking boot image
boot_patch.sh: line 87: ./magiskboot: Permission denied
boot_patch.sh: line 117: ./magiskboot: Permission denied
boot_patch.sh: line 148: ./magiskboot: Permission denied
boot_patch.sh: line 150: rm: Permission denied
boot_patch.sh: line 177: ./magiskboot: Permission denied
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
Failed!
! Installation failed

Any ideas what's going wrong here ?

Seems like installer cannot gain root access or something...
[Magisk] shakalaca:
Can you install Android Terminal on your device and execute 'which sh' ? I want to know if the app is using another shell.
[Magisk] Harshiv989:
[MENTION=1813976]shakalaca[/MENTION], I tried the Jack pal's emulator, output of "which sh" w/o quotes is "/system/bin/sh".

The file at "/system/bin/sh" is not a symlink so I doubt it has been touched at all. The output stays same with root shell.

By the way is the Magisk version 16 still in experimental branch? because I'm quite sure I've set update option for stable branch.
[Magisk] demonoidmaster:
Why not use v16 instead
[Magisk] Tattvamasi:
Yes I did/do flash the pachted image and haven't tried to flash the magisk.zip through TWRP.

So that can be done in combination with OxygenOS 5.0.2 without bricking the phone?
[Magisk] vMAC:
This was an old post.

I am using 16.0 now and still same issue.
[Magisk] Wolfcity:
Yes, you can try to flash the magisk16.zip through TWRP. If you get a bootloop you can boot into TWRP again and flash the actual magisk uninstaller (see OP) and/or the stock boot.img, TWRP can flash img files too, just change from zip to img in the install area and choose "boot".

This can be done with fastboot too ( fastboot flash boot boot.img ).
[Magisk] demonoidmaster:
Might wanna uninstall and reinstall magisk then, though just to be safe wipe /system and reinstall your rom, gapps, etc etc before magisk, then flash your kernel of choice if you use one

As for modules, some of them (if installed through twrp) will screw up the /magisk folder, wiping everything from it so you're better off installing via magisk app after your device finishes booting
[Magisk] Sam Nakamura:
Hey, thanks for the suggestion, on my mediatek device I extracted the magisk manager apk from your custom magisk 16 zip, changed the update channel in MagiskManager to custom and copied the URL from the mentioned post in there, I hope I didn't confuse something about the process, anyway when I start to patch the boot.img from within magisk manager by choosing the correct image file it just jumps back to the magisk manager main screen not starting the download or even showing the usual terminal output / script...

If I try to patch the boot.img (exact same procedure) on my 3t I get the old 6kb boot image output

Here's the log of the 6kb patching:

https://drive.google.com/file/d/18SKKzegwAwKlfmwbHCa5hiIQ5s_mrF36/view?usp=drivesdk

That's the boot image im talking about

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

That's the recovery log when flashing the custom magisk 16 in TWRP on the MTK device, it aborts the installation "can't detect ramdisk" - that what happens with magisk eversince but patching via magisk manager usually works, except this time...

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

-------------

This of course isn't a important issue, I just wanted to give feedback and let you know :)

If I can help in any additional way please let me know...
[Magisk] vMAC:
Tried that still same issue. Says I'm rooted, says Magisk installed, but can't download/install any modules.

01-14 08:17:10.499 599 599 I Magisk : Magisk v16.0(1600) daemon started
01-14 08:17:10.617 599 612 I Magisk : ** post-fs mode running
02-28 00:40:37.391 599 719 I Magisk : ** post-fs-data mode running
02-28 00:40:37.394 599 719 I Magisk : * Creating /sbin overlay
02-28 00:40:37.394 599 719 I Magisk : * Mounting mirrors
02-28 00:40:37.395 599 719 I Magisk : bind_mount: /sbin/.core/mirror/system
02-28 00:40:37.395 599 719 I Magisk : mount: /sbin/.core/mirror/vendor
02-28 00:40:37.396 599 719 I Magisk : bind_mount: /sbin/.core/mirror/bin
02-28 00:40:37.396 599 719 I Magisk : * Setting up internal busybox
02-28 00:40:37.406 599 719 I Magisk : * Merging /data/adb/magisk_merge.img -> /data/adb/magisk.img
02-28 00:40:37.676 599 719 I Magisk : * Mounting /data/adb/magisk.img
02-28 00:40:37.871 599 719 I Magisk : * Running post-fs-data.d scripts
02-28 00:40:37.871 599 719 I Magisk : * Running module post-fs-data scripts
02-28 00:40:37.872 599 719 I Magisk : * Loading modules
02-28 00:40:37.872 599 719 I Magisk : * Enabling systemless hosts file support
02-28 00:40:37.872 599 719 I Magisk : bind_mount: /system/etc/hosts
02-28 00:40:37.873 599 742 I Magisk : * Starting MagiskHide
02-28 00:40:37.873 599 742 I Magisk : hide_utils: Hiding sensitive props
02-28 00:40:37.873 599 742 I Magisk : hide_list: [com.google.android.gms.unstable]
02-28 00:40:37.919 599 742 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-28 00:40:38.412 599 961 I Magisk : ** late_start service mode running
02-28 00:40:38.412 599 961 I Magisk : * Running service.d scripts
02-28 00:40:38.412 599 961 I Magisk : * Running module service scripts
02-28 00:40:39.121 599 742 I Magisk : proc_monitor: zygote ns=mnt:[4026533937] zygote64 ns=mnt:[4026533938]
02-28 00:40:55.628 599 742 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=3761 ns=mnt:[4026533964])
02-28 00:41:00.835 599 742 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4613 ns=mnt:[4026534137])
02-28 00:41:59.376 7652 7652 I Magisk : Create /data/adb/magisk_merge.img with size 64M
02-28 00:41:59.678 7654 7654 E Magisk : mount /dev/block/loop1->/dev/tmp/magisk_img failed with 22: Invalid argument
[Magisk] Adrian312:
Hi

Having am issue installing anything from repo. Tried downgrade to 15.3 same issue. Please see logs
[Magisk] Ja_som:
Try to delete data for MM, it helped to me.
[Magisk] Adrian312:
No change?
[Magisk] Adrian312:
Tried to uninstall Magisk along with manager. Rebooted. Back to twrp install Magisk 16. I was able to install bunch of modules. Rebooted to have them active. They are NOT. For example Oneplus camera M is for sure not active. Now i cant install anything from repo or phone via magisk.

I am really desperate. Anyone?

Update: i reverted back to xxx rom 9.8 from 9.9 and its working now. Something odd with my setup and that versio.

Thanks
[Magisk] SacredDeviL666:
Thread Cleaned.

Removed few OT discussions and moved few to Magisk General Discussion thread :good:
[Magisk] ArmynC:
When I try to install for the first time magisk trough the manager (recommended way) all goes good.. it get me to the "console" then at a final.. it says.. unable to repack the boot image..

Samsung S5 (Qualcomm)

Android 6.0.1

Rooted

- Device platform: arm
- Extracting files
- Patch boot/ramdisk image: /dev/block/mmcblk0p15
boot_patch.sh: ./util_functions.sh: line 15: ps: Permission denied
boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied
boot_patch.sh: line 75: chmod: Permission denied
boot_patch.sh: line 78: ./magiskinit: Permission denied
- Unpacking boot image
boot_patch.sh: line 87: ./magiskboot: Permission denied
boot_patch.sh: line 117: ./magiskboot: Permission denied
boot_patch.sh: line 148: ./magiskboot: Permission denied
boot_patch.sh: line 150: rm: Permission denied
boot_patch.sh: line 177: ./magiskboot: Permission denied
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
Failed!
! Installation failed
[Magisk] Sam Nakamura:
Latest Magisk Manager still fails to patch a mtk boot image, after clicking install -> patch boot -> choosing the right "boot.img file" for a short moment a all white screen pops up before it returns to main screen of magisk manager... No download starts, nothing

LOG

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

For reference, same issue I previously described with former version, note that it used to work flawlessly til v16, direct patching never worked but patching from magisk manager did...

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75717208
[Magisk] Jyrka98:
Termux's 'su' is just a shell script
[Magisk] iDoddyc:
OOS 5.02 OP3 After update magisk 16.1 & manager, safetynet false
[Magisk] jackeagle:
Mod Edit

Thread Cleaned.

Back to topic Everyone. Do not deviate from the topic of this thread.

Treat all members with equal respect. If you find something inappropriate then use Report System and report to moderators. Do not indulge in arguments among yourself this will just clutter the thread and deviate from the topic.

Further such instances will attract actions against offenders account.

I hope this won't be repeated in future.

jackeagle

Forum Moderator
[Magisk] dredq:
No never used. I also did clean flashes. Still bootloops not sure why.
[Magisk] siealex:
My Nexus 5x still randomly refuses to boot past the bootloader Google logo. Some people on our local forum reported that it happens only with encrypted partitions. No logs at all, because the device even does not start booting. Can this be fixed in the future?
[Magisk] Donric13:
Hi. Dont know if it's the right place to post some logs. There are still some problems installing magisk modules in dp1 on my pixel xl. Installation through twrp works. Modul JDSP isn't working properly after install (shows as installed in magisk but sound in JDSP has heavy distorsions). Btw nice work to have root in such a shirt term in dp1! Thanks a lot.
[Magisk] Jaymin.0.1910:
It seems like Magisk bundled busybox does not have -t flag for mke2fs

Can you run

mke2fs -t ext4 /cache/tmp.img 8M

and see if that creates an ext4 image in /cache ??

If the above code succeeded, then module developers might need to make some call mke2fs from the update-binary instead of simply calling mount_magisk_img() function
[MENTION=4470081]topjohnwu[/MENTION], [MENTION=1813976]shakalaca[/MENTION] and other Magisk contributors, I don't have a Pixel, so can't test, but replacing the line 66 in img.c from

ret = exec_command_sync("mke2fs", "-b", "4096", "-t", "ext4", img, size_str, NULL);

to

ret = exec_command_sync("/system/bin/mke2fs", "-b", "4096", "-t", "ext4", img, size_str, NULL);

will fix this issue
[Magisk] Donric13:
Thanks for reply. I don't have deep knowledge of these things.... Should i run this command in terminal as root? Then i can try and report (and hope it doesn't make my device to explode....).
[Magisk] Jaymin.0.1910:
Yes, run it from a root shell and see if that creates an ext4 image in /cache
[Magisk] jcmm11:
On Oreo on a Nexus 5X the toybox version (/system/bin/) works the BusyBox version (/system/xbin/) doesn't. You're correct, no -t option.

I don't see this being any different on a different device. PATH prefers /system/bin/

This can be a problem running from recovery where BusyBox is preferred and system often isn't mounted.
[Magisk] Telperion:
walleye:/ $ su
walleye:/ # mke2fs -t ext4 /cache/tmp.img 8M
mke2fs 1.43.3 (04-Sep-2016)
Creating regular file /cache/tmp.img
Creating filesystem with 8192 1k blocks and 2048 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

walleye:/ #
[Magisk] jenslody:
It's already known. Unfortunately [MENTION=4470081]topjohnwu[/MENTION] will not be available before next weekend, if at all.
[Magisk] SacredDeviL666:
Thread Cleaned.

Please note this is a dev thread specially a beta testing thread to improve the upcoming builds of magisk & iron out possible bugs before its stable.

Kindly keep this thread on topic as clearly mentioned in OP

Thank you for your understanding.
[Magisk] Jaymin.0.1910:
Thanks , you helped me fix installations for my module " MC's Charging Controller ", and actully, when using libsu, PATH actually prioritizes busybox, since the module template mounts /system, there will not be any problem

Thanks, you also helped me fix installations for my module

Thanks for letting me know, so I was a bit later

Great :good:
[Magisk] JocPro:
Hello there.

16.1 broke my Contacts access. Any app that uses Contacts silently closes after less than a second. That includes Phone and Contacts apps.

Reverting to 16.0 fixed it.

Android 7.0 - Elephone P9000 (MT6755)
[Magisk] Didgeridoohan:
And as always, for anyone posting about issues in this thread:

Logs or it didn't happen™
[Magisk] Didgeridoohan:
You're in the completely wrong thread. Take a look here: https://xdaforums.com/showpost.php?p=75866229&postcount=5514

There's a dedicated Pokemon thread. Please use that instead...
[Magisk] JoLander:
Hi, I own a quite old Tablet Cube Talk 9X (U65GT) on which I flashed a special Version of the Resurrection Remix ROM based on Android 6.0.1.

The Tables works fine so far and the ROM has already included a Superuser functionality.

Nevertheless, I would like to install Magisk on it as I use it in my other devices, too.

Unfortunately, flashing failed with Error 1.

I attached the recovery.log here and I can clearly see an out-of-memory exception in the logfile.

Can somebody explain which memory I ran out of ?

Maybe I can manage the Installation if I know where to free up space......
[Magisk] Jaymin.0.1910:
Seems to have occured while Magisk was detecting boot image signature status
[Magisk] JoLander:
Is this something I can handle ??
[Magisk] Jaymin.0.1910:
I really do not have an Idea, I never mess with the custom recovery stuff, you can try patching ( via Magisk Manager ) and then flashing the image
[Magisk] glewo45:
I can't install module both in magisk 16 and even 16.1 please help,i'm on stock rom Moto g5s plus

Log attached,failed while try to install greenify modul ,same result while installing other module,