cannot install magisk modules (have tried answers in other threads) - Magisk

every time i try to install a module with magisk i get the magisk_mount.img failed message. i cannot install the zip files using twrp either. xposed modules work fine. my file system is not f2fs so i dont think that fix will help. any suggestions will be appreciated. thanks
phone: bv9000 pro
android: 7.1.1
magisk: v18
twrp recovery ( not encrypted have access to all files)

If you can post logs it's easier to help. In your case, the installation log, recovery log and Magisk log could be interesting to see.

log
- Copying zip to temp directory
- Installing ViPER4Android_FX-v3.1.zip
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/unityfiles/tools.tar.gz
inflating: common/unityfiles/util_functions.sh
Unzipping files...
*******************************************
* ViPER4Android FX *
*******************************************
* v3.1 *
* by ViPER520, ZhuHang, Ahrion, Zackptg5 *
*******************************************
- Mounting /data, /cache
- Magisk install detected
- Mounting /system, /vendor
- Creating /data/adb/magisk_merge.img with size 64M
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
Create /data/adb/magisk_merge.img with size 64M
e2fsck 1.42.9 (28-Dec-2013)
mount /sbin/.magisk/block/loop09->/dev/tmp/magisk_img failed with 13: Permission denied
! /data/adb/magisk_merge.img mount failed...
! Installation failed
after trying a fix i saw on another thread now i just get this:
- Copying zip to temp directory
! Invalid Uri
! Installation failed
reinstalled magisk now getting the same results as first log

Related

CWM fail to restore /data

Hello. Three days ago i made a backup of vanir rom using cwm , then i flashed miui ( philz touch recovery) and now i cant restore my vanir backup, only system backup. I cant restore even from cwm. I guess backup is not corrupted , as it was made without problems and i didnt touched it. I also tried to mount /data ,format ..still fail to restore /data. I attached an recovery log.
Any idea? Thanks.
I saw that recovery log didnt got attached first time, so here is it : http://m.uploadedit.com/b044/1421324866971.txt .
Force said:
Hello. Three days ago i made a backup of vanir rom using cwm , then i flashed miui ( philz touch recovery) and now i cant restore my vanir backup, only system backup. I cant restore even from cwm. I guess backup is not corrupted , as it was made without problems and i didnt touched it. I also tried to mount /data ,format ..still fail to restore /data. I attached an recovery log.
Any idea? Thanks.
Click to expand...
Click to collapse
Try to flash some other kernel with CWM and do restore with it.
According to the recovery log, the backup is somewhat restoring to the wrong directory. Seems the data partition was corrupted before making the backup.
Code:
I:data/
I:data/lost+found/
I:data/lost+found/#16436/
I:data/lost+found/#16436/softap.conf
I:data/lost+found/#16436/p2p_supplicant.conf
I:data/lost+found/#16436/wpa_supplicant.conf
I:data/lost+found/#16436/entropy.bin
I:data/lost+found/#16440/
shut_down said:
Try to flash some other kernel with CWM and do restore with it.
Click to expand...
Click to collapse
Still fail. I also tried TWRP (it doesnt see my backup) and Philz recovery.
Jtfk said:
According to the recovery log, the backup is somewhat restoring to the wrong directory. Seems the data partition was corrupted before making the backup.
Code:
I:data/
I:data/lost+found/
I:data/lost+found/#16436/
I:data/lost+found/#16436/softap.conf
I:data/lost+found/#16436/p2p_supplicant.conf
I:data/lost+found/#16436/wpa_supplicant.conf
I:data/lost+found/#16436/entropy.bin
I:data/lost+found/#16440/
Click to expand...
Click to collapse
Damn
Anyway, i took a log with philz recovery too:
Code:
>> Restoring /data...
couldn't find old .img format
Found new backup image: /storage/sdcard1/clockworkmod/backup/2015-01-10.08.44.32//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Press Back to cancel.
tar: can't remove old file data/lost+found/#115233: Is a directory
Error while restoring /data!
press any key to continue.
I:skiping set_bootloader_message: no /misc
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Force said:
Still fail. I also tried TWRP (it doesnt see my backup) and Philz recovery.
Damn
Anyway, i took a log with philz recovery too:
Code:
>> Restoring /data...
couldn't find old .img format
Found new backup image: /storage/sdcard1/clockworkmod/backup/2015-01-10.08.44.32//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Press Back to cancel.
tar: can't remove old file data/lost+found/#115233: Is a directory
Error while restoring /data!
press any key to continue.
I:skiping set_bootloader_message: no /misc
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Click to expand...
Click to collapse
did you tried to flash kernel with which you made CWM backup ?
if not try it
and it seems your partitions are corrupt so 1st install stock firmware via odin and then flash kernel with which u made back and after that wipe "all" thingsand then restore backu
jineshpatel30 said:
did you tried to flash kernel with which you made CWM backup ?
if not try it
and it seems your partitions are corrupt so 1st install stock firmware via odin and then flash kernel with which u made back and after that wipe "all" thingsand then restore backu
Click to expand...
Click to collapse
I tried what you said and it didnt work. I guess there is nothing i can do...
Force said:
I tried what you said and it didnt work. I guess there is nothing i can do...
Click to expand...
Click to collapse
That's sad...take 3-4 hrs spare to setup entire settings n phone again -_-
Btw one suggestion from me...next time when you make backup (or one more backup) using "temporary cwm" by shaan it works over all roms and kernel.
jineshpatel30 said:
That's sad...take 3-4 hrs spare to setup entire settings n phone again [emoji14] -_-
Btw one suggestion from me...next time when you make backup (or one more backup) using "temporary cwm" by shaan it works over all roms and kernel.
Click to expand...
Click to collapse
Thanks for suggestion. By the way, my backup size was 2gb and i dont remember all my stuff

Supersu 2.67 no root

Hey guys I have a problem with the latest Supersu. I can't get root with my Samsung Galaxy S6 edge plus. So I tried an older version. That worked very well. Could you take a look at the log, please? I don't know what's the problem with that.
Code:
*****************Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 11/2048 files, 1166/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mknod: /dev/block/loop0: File exists
ioctl LOOP_SET_FD failed: Device or resource busy
- Mounting /system, /data and rootfsrm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
- Extracting filesrm: can't remove '/su/bin/sukernel': No such file or directory
rm: can't remove '/data/SuperSU.apk': No such file or directory
rm: can't remove '/su/su.d/000000deepsleep': No such file or directory
- System-less mode, boot image support requiredsukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/sda5] ...
magic: [ANDROID!]
kernel: [18869536] (18870272) @ 0x10008000
ramdisk: [5367784] (5367808) @ 0x11000000
second: [0] (0) @ 0x10f00000
tags: @ 0x10000100
page size: 2048
unused: [0x0013b000] [0x00000000]
dtb(?): [1290240] (1290240)
name: []
command line: []
extra command line: []
id: [0xcb1a9d371fd0d7b82fa23c023a0cbffc281ecd60000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk.packed] ...
Decompressing [5367784] --> ungzip: inflate: -3
failed
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
Install from sdcard complete.
Luna447 said:
Hey guys I have a problem with the latest Supersu. I can't get root with my Samsung Galaxy S6 edge plus. So I tried an older version. That worked very well. Could you take a look at the log, please? I don't know what's the problem with that.
Code:
*****************Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 11/2048 files, 1166/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mknod: /dev/block/loop0: File exists
ioctl LOOP_SET_FD failed: Device or resource busy
- Mounting /system, /data and rootfsrm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
- Extracting filesrm: can't remove '/su/bin/sukernel': No such file or directory
rm: can't remove '/data/SuperSU.apk': No such file or directory
rm: can't remove '/su/su.d/000000deepsleep': No such file or directory
- System-less mode, boot image support requiredsukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/sda5] ...
magic: [ANDROID!]
kernel: [18869536] (18870272) @ 0x10008000
ramdisk: [5367784] (5367808) @ 0x11000000
second: [0] (0) @ 0x10f00000
tags: @ 0x10000100
page size: 2048
unused: [0x0013b000] [0x00000000]
dtb(?): [1290240] (1290240)
name: []
command line: []
extra command line: []
id: [0xcb1a9d371fd0d7b82fa23c023a0cbffc281ecd60000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk.packed] ...
Decompressing [5367784] --> ungzip: inflate: -3
failed
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
Install from sdcard complete.
Click to expand...
Click to collapse
Is this a custom kernel?
Please post your boot.img
It's the latest arter Kernel for the s6e+. I think it's the v9.4.
E: http://arter97.com/browse/exynos7420/kernel/9.4/g928fcig this one.
So do you think the kernel is the problem here?
Luna447 said:
It's the latest arter Kernel for the s6e+. I think it's the v9.4.
E: http://arter97.com/browse/exynos7420/kernel/9.4/g928fcig this one.
So do you think the kernel is the problem here?
Click to expand...
Click to collapse
It's probably not compressed with gzip. SuperSU currently only supports gzip compression to modify kernels.
Chainfire said:
It's probably not compressed with gzip. SuperSU currently only supports gzip compression to modify kernels.
Click to expand...
Click to collapse
Oh I see! So what can I do to make it work? Simply extract and recompress is with a tool?
Luna447 said:
Oh I see! So what can I do to make it work? Simply extract and recompress is with a tool?
Click to expand...
Click to collapse
Nothing really. After looking at that kernel, it seems he completely disabled SELinux. That's a case the installer doesn't cover (it should), so it can just use a /system based root instead of systemless.
That and adding support for LZ4 should both fix the problem, but they are both things I need to do.
What you can try is, in recovery, execute this shell command:
Code:
echo SYSTEMLESS=true>>/data/.supersu
That might do the trick.
Chainfire said:
Nothing really. After looking at that kernel, it seems he completely disabled SELinux. That's a case the installer doesn't cover (it should), so it can just use a /system based root instead of systemless.
That and adding support for LZ4 should both fix the problem, but they are both things I need to do.
What you can try is, in recovery, execute this shell command:
Code:
echo SYSTEMLESS=true>>/data/.supersu
That might do the trick.
Click to expand...
Click to collapse
First of all, thanks for answering. But I'm not sure if I'm doing this right.
So I boot my phone into recovery.
Then I open up the cmd on my pc and navigate to the adb folder.
Now I type in "adb shell" and execute the code you provided above?
(c:\adb-tools>adb shell
~ # echo SYSTEMLESS=true>>/data/.supersu)
Yes, and then you flash SuperSU again.
Chainfire said:
Yes, and then you flash SuperSU again.
Click to expand...
Click to collapse
Hm unfortunately it didn't work. Can you recommend any good Kernel for the s6e+?
I really would like to use your latest Supersu due to the deep sleep issue I'm facing with my phone.
I feel the same, with CM 13 a Galaxy S2 i9100. If I install the superuser without installing the rom no problem, but when the ROM is installed, gives the same error
loparaan said:
I feel the same, with CM 13 a Galaxy S2 i9100. If I install the superuser without installing the rom no problem, but when the ROM is installed, gives the same error
Click to expand...
Click to collapse
Mate, I had the same problems on i9100 after installing a Lanchon kernel.
But I'd flashed a DorimanX one (https://drive.google.com/folderview?id=0B3ApZsjOd2bzWjBBMHc2SWNUSlE&usp=sharing), formatted sdcard0, and then tried to install SuperSU (before a firmware). And it worked! Then installed CM13 and got success!
blackb00m said:
Mate, I had the same problems on i9100 after installing a Lanchon kernel.
But I'd flashed a DorimanX one (https://drive.google.com/folderview?id=0B3ApZsjOd2bzWjBBMHc2SWNUSlE&usp=sharing), formatted sdcard0, and then tried to install SuperSU (before a firmware). And it worked! Then installed CM13 and got success!
Click to expand...
Click to collapse
Before installing the 13 cm, I have no problems with the installation of SuperSU, also it worked out. But when installing the CM13 the first time, the SuperSU is lost.
I'll try with that kernel to see if you let me install it. Thank you
Sumsung Galaxy s4 shv_e330k root
Got a similar problem with my LG G3 running Marshmallow (rooted with method and tools supplied here).
Oddly enough, the SuperSU 2.52 beta from the above link works flawlessly, but the 2.67 beta (and 2.65 stable) both get the "decompressing ramdisk, failure aborting" issue.
Attached recovery log in case its needed to troubleshoot!
You can just use the zips from this thread: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 This will force it in system mode so it will not even attempt to do it in system-less
Xmaster24 said:
You can just use the zips from this thread: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 This will force it in system mode so it will not even attempt to do it in system-less
Click to expand...
Click to collapse
Worked like a charm! Thanks!
Palaryel said:
Worked like a charm! Thanks!
Click to expand...
Click to collapse
No problem this should fix the update problems for everyone on this forum
I have a similar problem! :/ - SAMSUNG GT-i9100GSMH + lineageos 14.1 + TWRP-3.0.2-1-i9100 - SuperSU-v2.79 NO ROOT :/
Odin install Siyah-s2-v6.0b5 Kernel +Recovery by Gatox Tutorialex.tar
AND AFTER recovery install TWRP: recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
+
lineage-14.1-20170510-nightly-i9100-signed.zip (android 7)
No apps Root lineage :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SuperSU-v2.79-201612051815.zip
+
SuperSU GooglePlay
Install SUPERSU and NoRoot:
Do you think the solution is???
the same problem
also the same problem no root D:

Creating new module and phone is bootlooping

I've got a HTC 10 and trying to do something simple by replacing the file located at
Code:
/system/customize/resource/HTC_Sense5_Boot.mp3
with a zero size file so that when it boots up it doesn't play.
I've copied the template from here and modified the following 2 files.
module.sh
Code:
id=disablehtcbootsound
name=Disable HTC Boot Sound
version=v1
versionCode=1
author=Raven
description=Disables HTC boot sound
template=1400
config.sh
Code:
AUTOMOUNT=true
PROPFILE=false
POSTFSDATA=false
LATESTARTSERVICE=false
print_modname() {
ui_print "*******************************"
ui_print " DISABLE HTC BOOT SOUND "
ui_print "*******************************"
}
REPLACE="
/system/customize/resource/HTC_Sense5_Boot.mp3
"
set_permissions() {
set_perm_recursive $MODPATH 0 0 0755 0644
}
It installs fine but as soon as I reboot the phone it gets stuck at the green HTC logo and doesn't do anything from then on. I've checked logfile and it looks like I might be using the wrong command in config.sh. Anyone got tips on what I need to do???
logfile
Code:
- Copying zip to temp directory
- Installing disablehtcbootsound.zip
- Mounting /system, /vendor, /data, /cache
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: config.sh
inflating: module.prop
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
*******************************
DISABLE HTC BOOT SOUND
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/magisk_merge.img with size 64M
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
- Mounting /data/magisk_merge.img to /dev/magisk_merge
- Extracting module files
touch: /dev/magisk_merge/disablehtcbootsound/system/customize/resource/HTC_Sense5_Boot.mp3/.replace: Not a directory
update-binary[138]: can't create /dev/magisk_merge/disablehtcbootsound/system/customize/resource/HTC_Sense5_Boot.mp3/.replace: Not a directory
chmod: /dev/magisk_merge/disablehtcbootsound/system/customize/resource/HTC_Sense5_Boot.mp3/.replace: Not a directory
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: system/
creating: system/customize/
creating: system/customize/resource/
inflating: system/customize/resource/HTC_Sense5_Boot.mp3
inflating: system/placeholder
- Setting permissions
- Done
- All done!
Don't add the file to the REPLACE part of config.sh. That's for directories, not files. It even says so in the instructions ("List all directories")...
Just add the empty file under /system/customize/resource/ in your module and you're good to go.
Ok so to make sure I've done this correctly, I've left the template config.sh untouched, put the empty mp3 under /system/customize/resource/, zip it all together and flash?
I've done just that and it still bootloops... the log seems fine this time however when I go into the magisk folder there is still nothing aside from 2 files. (update and module.prop)
I've tried flashing from TWRP and same result still.
Code:
- Copying zip to temp directory
- Installing disablehtcbootsound.zip
- Mounting /system, /vendor, /data, /cache
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: config.sh
inflating: module.prop
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
*******************************
DISABLE HTC BOOT SOUND
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/magisk_merge.img with size 64M
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
- Mounting /data/magisk_merge.img to /dev/magisk_merge
- Extracting module files
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: system/
creating: system/customize/
creating: system/customize/resource/
inflating: system/customize/resource/HTC_Sense5_Boot.mp3
inflating: system/placeholder
- Setting permissions
- Done
- All done!
nullo said:
Ok so to make sure I've done this correctly, I've left the template config.sh untouched, put the empty mp3 under /system/customize/resource/, zip it all together and flash?
I've done just that and it still bootloops... the log seems fine this time however when I go into the magisk folder there is still nothing aside from 2 files. (update and module.prop)
I've tried flashing from TWRP and same result still.
Code:
- Copying zip to temp directory
- Installing disablehtcbootsound.zip
- Mounting /system, /vendor, /data, /cache
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: config.sh
inflating: module.prop
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
*******************************
DISABLE HTC BOOT SOUND
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/magisk_merge.img with size 64M
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
- Mounting /data/magisk_merge.img to /dev/magisk_merge
- Extracting module files
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: system/
creating: system/customize/
creating: system/customize/resource/
inflating: system/customize/resource/HTC_Sense5_Boot.mp3
inflating: system/placeholder
- Setting permissions
- Done
- All done!
Click to expand...
Click to collapse
Remove the placeholder file in /system. Mounting files or folders to the root of /system that doesn't previously exist can cause bootloops.
Disable HTC Boot Sound
Haha wowsers that was easy! Thanks heaps mate! All works now without the placeholder in the system folder.
For anyone who wants to have the boot sound on your HTC disabled and systemless, I have the module attached. If for some reason it causes you to bootloop, I've got an uninstaller which I used in TWRP which helped me heaps when testing haha.

Magisk mount failed when trying to install modules

Has all been working fine until today.
Tried installing a font and I get a failed message.
Try installing via TWRP and it hangs until I force reboot.
Happening with all modules.
My current installed ones are fine
Greenify
Single user mod
Nova & Google now companion
This is the error log trying install magisk hide as an example.
- Copying zip to temp directory
- Installing MagiskHide_Props_Config-v2.3.0-v19.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/post-fs-data.sh
inflating: common/prints.sh
inflating: common/propsconf_conf
inflating: common/propsconf_late
inflating: common/propsconf_post
inflating: common/util_functions.sh
inflating: config.sh
inflating: module.prop
*******************************
MagiskHide Props Config v2.3.0
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/adb/magisk_merge.img with size 64M
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
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
Cannot mount image!
! /data/adb/magisk_merge.img mount failed...
Failed!
! Installation failed
Any help would be appreciated! As I really don't want to format and start again.
Lg G6
Twrp 3.2.1
Use lates 19.0 beta to fix

Magisk Wifi Boarding (Failed)

- Copying zip to temp directory
- Installing Wifi_Bonding_(Qualcomm)-1.8.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: config.sh
inflating: module.prop
*******************************
Magisk WiFi Bonding
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/adb/magisk_merge.img with size 64M
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
e2fsck 1.43.3 (04-Sep-2016)
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
- Extracting module files
- Migrating WCNSS_qcom_cfg.ini
- Migration FAILED.
Please report it to the developer with
your WCNSS_qcom_cfg.ini path.
- Setting permissions
- Done
- All done!

Categories

Resources