Newly downloaded modules don't mount after reboot - Magisk

BUG
on Magisk v15.3 (non-beta)
on Magisk Manager 5.5.5
I can install modules after downloading and installing Magisk for the first time. But when I reboot my phone, I can no longer install modules. Error is:
Code:
- Found /data/adb/magisk_merge.img
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/magisk_merge.img mount failed...
Failed!
! Installation failed
Have tested multiple times on Xiaomi Mi A1.

Related

Modules not appearing as installed nor working

I just tried installing Magisk v9 with the current Xposed module on a YotaPhone 2 running Android 5.0, but it seems that the module doesn't correctly initialize.
I downloaded and installed the Xposed SDK 21 module in Magisk Manager v2.5. After reboot, however, the module list in Magis Manager was empty (not even phh's Superuser was visible there, which I previously flashed in recovery). However, the Magisk log shows that the Xposed script is executed:
Code:
** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
Preparing modules
Bind mount dummy system
Bind mount module items
post-fs-data: /magisk/xposed/post-fs-data.sh
Enabling systemless hosts file support
Mount: /magisk/.core/hosts
Bind mount system mirror
Mount: /system
Bind mount mirror items
** Magisk late_start service mode running...
service: /magisk/phh/service.sh
phh: Live patching sepolicy
phh: Mounting supath
phh: Starting su daemon
The Xposed Installer now shows on the status screen that Xposed is installed but not active. An Xposed log file in /data/data/de.robv.android.xposed.installer/log doesn't exist. Logcat has no entries for Magisk nor Xposed. Also, the "Enable systemless hosts" checkbox in Magisk Manager isn't active anymore after reboot, even if it clearly is configured that way according to the logs. Is this a bug in Magisk or am I doing something wrong?

[Solved] Viper4android

Hey there,
I accidentally updated V4a today and now it is not working anymore. Is there any chance to get the version before the latest.
Solved: dared to flash Magisk 11. Everything is working again
Magisk says 2.5.0.5 and viper driver status says 2.5.0.4
The Magisk Log
Code:
** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
/data/magisk_merge.img found
/data/magisk.img found, attempt to merge
/dev/block/loop0 /data/magisk.img
/dev/block/loop1 /data/magisk_merge.img
Merging: v4a
Merge complete
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
Mount: /dev/magisk/dummy/system/lib/soundfx
* Stage 3: Mount module items
Mount: /magisk/v4a/system/lib/soundfx/libv4a_fx_ics.so
Mount: /magisk/v4a/system/etc/audio_effects.conf
Mount: /magisk/v4a/vendor/etc/audio_effects.conf
* Stage 4: Execute module scripts
post-fs-data: /magisk/v4a/post-fs-data.sh
post-fs-data: /magisk/xposed/post-fs-data.sh
Xposed: Mount: /magisk/xposed/system/lib64/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib64/libart.so
Xposed: Mount: /magisk/xposed/system/lib64/libart-disassembler.so
Xposed: Mount: /magisk/xposed/system/lib/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib/libart.so
Xposed: Mount: /magisk/xposed/system/lib/libart-compiler.so
Xposed: Mount: /magisk/xposed/system/bin/patchoat
Xposed: Mount: /magisk/xposed/system/bin/oatdump
Xposed: Mount: /magisk/xposed/system/bin/dex2oat
Xposed: Mount: /magisk/xposed/system/bin/app_process64
Xposed: Mount: /magisk/xposed/system/bin/app_process32
* Stage 5: Mount mirrored items back to dummy
Mount: /dev/magisk/mirror/system/lib/soundfx/libvisualizer.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libreverbwrapper.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcomvoiceprocessing.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcomvisualizer.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcompostprocbundle.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libldnhncr.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libeffectproxy.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libdownmix.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libdirac.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libbundlewrapper.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libaudiopreprocessing.so
** Magisk late_start service mode running...
just remove libvolumelistener.so
me 2 viper doesnt work for me :/
ViPER causes bootloop for me too.
ryaniskira said:
ViPER causes bootloop for me too.
Click to expand...
Click to collapse
It did not cause bootloops on my phone. It just did not work. Driver status unsupported...
ViPER won't let my phone boot at all. Does it still need ElementalX even on Magisk?
Me too. Take me a lot time to rescure.
Same here, Dolby Atmos also. I think none of them are compatible with 7.1.*
Anyone, prove me wrong?
Download and install Viper2505 Magisk module by topjohnwhu then reboot , download viper2505 on the official thread and install viper via apk. It will work after reboot.
And when driver status is okay but audio isn't being processed?
Iaa85 from Brazil with Oneplus 3t
Powered by AEX ROM
iaa85 said:
And when driver status is okay but audio isn't being processed?
Iaa85 from Brazil with Oneplus 3t
Powered by AEX ROM
Click to expand...
Click to collapse
turn off-on the master power in V4a.
i installed magisk module (flashed it) and now my S8 keeps booting to recovery, and doenst boot to system. help? Thanks!
raracin said:
i installed magisk module (flashed it) and now my S8 keeps booting to recovery, and doenst boot to system. help? Thanks!
Click to expand...
Click to collapse
Find the Mount-Magisk flashable zip in this forum and flash it via twrp. Then use file-manager in twrp, go to magisk folder and delete the viper module. Then try booting up.

Moto E4 Root with Magisk?

I am having super troubles getting the Moto E4 to work with Magisk root. Here are my logs:
Log for 13.1-13.3 (all do same thing) Magisk flash:
Code:
Updating partition details...
..done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/Magisk-v13.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
***********************
* Magisk v13.1 Installer
***********************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
- Creating /data/magisk.img
- Mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v13.1.zip'
Updating partition details...
...done
Log for 12.0 Magisk flash:
Code:
Installing zip file '/external_sd/Magisk-v12.0.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
***********************
Magisk v12.0 Boot Image Patcher
***********************
- Mounting /system(ro), /vendor, /cache, /data
- Device platform: arm
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/mmcblk0p37
- Unpacking boot image
- Checking patch status
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
..done
Seems to have worked but didn't. After I open and update manager it says no root.
Followed this here on the first page:
https://forum.xda-developers.com/moto-e4/help/root-question-t3626349
BUT:
Diverged to use Magisk rather than Phh SuperSU from this page, can't get 13.1-13.3 to flash though. Redid stock boot image and reflashed entire ROM a few times deleting cache, etc:
https://forum.xda-developers.com/moto-e4/help/root-question-t3626349/page2
Any ideas?
Thanks.
JD495 said:
I am having super troubles getting the Moto E4 to work with Magisk root. Here are my logs:
Log for 13.1-13.3 (all do same thing) Magisk flash:
Code:
Updating partition details...
..done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/Magisk-v13.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
***********************
* Magisk v13.1 Installer
***********************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
- Creating /data/magisk.img
- Mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v13.1.zip'
Updating partition details...
...done
Log for 12.0 Magisk flash:
Code:
Installing zip file '/external_sd/Magisk-v12.0.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
***********************
Magisk v12.0 Boot Image Patcher
***********************
- Mounting /system(ro), /vendor, /cache, /data
- Device platform: arm
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/mmcblk0p37
- Unpacking boot image
- Checking patch status
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
..done
Seems to have worked but didn't. After I open and update manager it says no root.
Followed this here on the first page:
https://forum.xda-developers.com/moto-e4/help/root-question-t3626349
BUT:
Diverged to use Magisk rather than Phh SuperSU from this page, can't get 13.1-13.3 to flash though. Redid stock boot image and reflashed entire ROM a few times deleting cache, etc:
https://forum.xda-developers.com/moto-e4/help/root-question-t3626349/page2
Any ideas?
Thanks.
Click to expand...
Click to collapse
Mine was rooted with Magisk but I just reset to permanently flash TWRP and I'm running into the same issues. Did you ever find a fix?

Unable to extract zip file

I've got a freshly installed Magisk v14, with manager 5.6.0, running on an Oukitel K10 with Android 7.1.1.
Version 15+ of Magisk causes a boot loop on this device, so I'm stuck on 14.
Anyway, installing downloaded Magisk modules from the zip file, or from the Downloads section in the manager, I get logs like:
Code:
- Copying zip to temp directory
- Installing Emoji_one-v1.311.zip
- Mounting /system, /vendor, /data, /cache
! Unable to extract zip file!
Failed!
! Installation failed
The MagiskManager directory does exist. I also deleted it and let the manager recreate it by downloading the magisk zip again. No change.
What can I do?
Might be an issue with unzip. Try if installing the Busybox module from the Downloads section works, and if it does, try installing modules again (after rebooting).
Installing BusyBox worked, but even after a reboot I get the same result when attempting to install other stuff. Also, BusyBox is listed under "Update Available" in the downloads section even though I already installed 1.27.2, twice.
norbolt said:
Installing BusyBox worked, but even after a reboot I get the same result when attempting to install other stuff. Also, BusyBox is listed under "Update Available" in the downloads section even though I already installed 1.27.2, twice.
Click to expand...
Click to collapse
That most likely means it did not work. Post the install log from installing the Busybox module.
Hm. Yes, the log doesn't seem as fine.
Code:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script
by osm0sis @ xda-developers
Mounting...
mount: bad /etc/fstab: No such file or directory
mount: bad /etc/fstab: No such file or directory
mount: bad /etc/fstab: No such file or directory
Extracting files...
update-binary[110]: unzip: not found
Installing...
Using architecture: arm64
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
umount: /dev/magisk_merge: No such file or directory
mount: losetup failed 1
mknod: /dev/block/loop0: File exists
losetup: /dev/block/loop0=/data//magisk_merge.img: Device or resource busy
mknod: /dev/block/loop1: File exists
Using path: /dev/magisk_merge/busybox-ndk/system/xbin
cp: busybox-arm64: No such file or directory
cp: bad 'busybox-arm64': No such file or directory
chown: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: No such file or directory
chmod: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: No such file or directory
cp: module.prop: No such file or directory
cp: bad 'module.prop': No such file or directory
cp: module.prop: No such file or directory
cp: bad 'module.prop': No such file or directory
Cleaning...
update-binary[189]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
update-binary[191]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
update-binary[210]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
Creating symlinks...
Unmounting...
umount: /system: Device or resource busy
umount: /data: Device or resource busy
umount: /cache: Device or resource busy
Done!
- All done!
Yeah, there's an issue with unzip:
Code:
update-binary[110]: unzip: not found
Might be an issue with your Magisk installation or a device thing, hard to say....
Have you tried installing a zip through recovery? If you can install the Busybox module in recovery it might fix things.
Didgeridoohan said:
Have you tried installing a zip through recovery? If you can install the Busybox module in recovery it might fix things.
Click to expand...
Click to collapse
I have not tried that. I currently have the stock recovery flashed. So I guess this means flashing TWRP, then flashing Busybox, and perhaps also attempting to flash Magisk itself through the recovery?
Hopefully I got that right. I'm a bit new to this.
norbolt said:
I have not tried that. I currently have the stock recovery flashed. So I guess this means flashing TWRP, then flashing Busybox, and perhaps also attempting to flash Magisk itself through the recovery?
Hopefully I got that right. I'm a bit new to this.
Click to expand...
Click to collapse
You don't have to install TWRP, you can just boot it:
Code:
fastboot boot recovery twrp.img
I attempted to install both Magisk and Busybox from TWRP, and while the Magisk installer seems to run fine, I get to allow root access to stuff in Android afterwards and I get the Magisk Manager and such, I still can't install Busybox. Also, it seems from the log that Magisk itself is also having some issues the UI isn't telling me about.
The main issue seems to be the following error:
Code:
I:[MTP] MtpServer::run fd: 26
E:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 19, exiting MtpServer::run loop
Searching Google for the above error returns very little help.
I pasted the entire log here, from me booting TWRP and attempting to install Magisk and Busybox a few times. The Busybox installer claims Magisk isn't installed.
I can't post links yet, so this is code:
Code:
http://paste.debian.net/1010746/
norbolt said:
I've got a freshly installed Magisk v14, with manager 5.6.0, running on an Oukitel K10 with Android 7.1.1.
Version 15+ of Magisk causes a boot loop on this device, so I'm stuck on 14.
Anyway, installing downloaded Magisk modules from the zip file, or from the Downloads section in the manager, I get logs like:
Code:
- Copying zip to temp directory
- Installing Emoji_one-v1.311.zip
- Mounting /system, /vendor, /data, /cache
! Unable to extract zip file!
Failed!
! Installation failed
The MagiskManager directory does exist. I also deleted it and let the manager recreate it by downloading the magisk zip again. No change.
What can I do?
Click to expand...
Click to collapse
hello,
Very simple solution for me at least.
i found this thread because the same thing just happened to me on g900t s5 running lineageOS. Magisk said couldnt extract Zip everytime.
My problem i believe was that i installed busybox from Apkpure and not playstore
Because when i uninstalled Busybox from apkpure then installed busybox from playtore the unzip errors are gone!
Maybe its because i has a bad copy of busybox?
Idk but that was the solution for me!
Hope this helps someone
Me helps install again magisk by twrp.
Install the es file explorer once and extract the zip at least once, It will show a list of programs by which to extract, select es file extractor and check the always button now go back to the magisk manager and try again you should be good to go.
magisk zip
My problem solved by typing real path.
I was use command to install a module using this code
Code:
twrp install sdcard/module.zip
Give an error, so i change to
Code:
twrp install /sdcard/module.zip
Everything ok.
alfanveykov said:
My problem solved by typing real path.
I was use command to install a module using this code
Code:
twrp install sdcard/module.zip
Give an error, so i change to
Code:
twrp install /sdcard/module.zip
Everything ok.
Click to expand...
Click to collapse
where I must try this command?
because I have same problem

Error installing Magisk

Hi.
I currently have super su installed and the device is rooted. However, what I want to accomplish (pokemon go spoofing) requires magisk. Its android 8.0 and I have twrp. When I go to install magisk via twrp, I get roughly this:
- Mounting /system, /vendor
- Target image: /dev/block/sda5
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by unsupported programs
!Please restore stock boot image
- Unmounting Partitions
Updater process ended with Error: 1
Error installing zip file '/sdcard/Download/Magisk-v17.1.zip
Updating partition details...
...done
No idea what to do from here. Do I need to get rid of super su? and how would I do that? Thank you all in advance.
https://www.didgeridoohan.com/magis..._another_systemless_root_solution_to_MagiskSU

Categories

Resources