Closed Y-ZD-heheka closed 1 year ago
Send dmesg and /proc/last_kmsg
(if exists)
Disable module (not remove), and execute this command:
(unshare to avoid damage mount)
unshare -m $(magisk --path)/.magisk/busybox/sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh
Tell me the result
Disable module (not remove), and execute this command:
(unshare to avoid damage mount)
unshare -m $(magisk --path)/.magisk/busybox/sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh
Tell me the result
.\adb.exe shell OnePlus9:/ $ unshare -m $(magisk --path)/.magisk/busybox/sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh /system/bin/sh: magisk: inaccessible or not found unshare: Operation not permitted
Type su
and paste!
Type
su
and paste!
Tried a few times,i can not boot up with magisk flashed,i have no su,sad
Try boot into safe mode
Try boot into safe mode
Only after flashing the original boot.img and system package can enter the system and the data is still there. Once sideload magisk.zip in recovery mode, it shows "qualcomm crashdump mode" directly after "powered by android" and cannot enter the system to select safe mode.sad
Did you have custom recovery, I can help you recover from that
With Magisk Delta
Did you have custom recovery, I can help you recover from that
i use the linesgeos recovery,color of purple
Did you have custom recovery, I can help you recover from that
it can execute adb shell
Did you have custom recovery, I can help you recover from that
i use the linesgeos recovery,color of purple
Flash Magisk Delta, and then creating these file (pick one):
/cache/.disable_magisk /persist/.disable_magisk /metada/.disable_magisk
Or:
magisk --remove-modules
Did you have custom recovery, I can help you recover from that
i use the linesgeos recovery,color of purple
Flash Magisk Delta, and then creating these file (pick one):
/cache/.disable_magisk /persist/.disable_magisk /metada/.disable_magisk
Cannot create ".disable_magisk" file in "recovery adb shell".
Cannot execute "magisk --remove-modules" command in "recovery adb shell". No right to operate the "/" directory.
I can't boot the system after I flashed "Magisk Delta", just like I flashed the original Magisk.
Maybe it's a problem with my hardware。I can only choose between "Magisk" and "system normal use".
Did you have custom recovery, I can help you recover from that
i use the linesgeos recovery,color of purple
Flash Magisk Delta, and then creating these file (pick one): /cache/.disable_magisk /persist/.disable_magisk /metada/.disable_magisk
Cannot create ".disable_magisk" file in "recovery adb shell".
Cannot execute "magisk --remove-modules" command in "recovery adb shell". No right to operate the "/" directory.
I can't boot the system after I flashed "Magisk Delta", just like I flashed the original Magisk.
Maybe it's a problem with my hardware。I can only choose between "Magisk" and "system normal use".
In recovery mode, you must mount all partitions
Cannot create ".disable_magisk" file in "recovery adb shell".
This doesn't work??
for s in cache persist metadata; do
mount /$s
touch /$s/.disable_magisk
done
Cannot create ".disable_magisk" file in "recovery adb shell".
This doesn't work??
for s in cache persist metadata; do mount /$s touch /$s/.disable_magisk done
OnePlus9:/ # for s in cache persist metadata; do
mount /$s touch /$s/.disable_magisk
d> done mount: '/cache' not in fstab mount: '/persist' not in fstab touch: '/persist/.disable_magisk': No such file or directory
lineageos recovery only mount system,i will try twrp later
Damn, why there is such broken recovery implementation 🤔
I successfully created the ".disable_magisk" file using "TWRP" and executed the "unshare" command with "SU" privileges. Unfortunately, the "last_kmesg" file was not found under "proc".
unshare -m $(magisk --path)/.magisk/busybox/sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh result:https://dpaste.org/3Gt4w
dmesg:https://dpaste.org/SiWBK
I successfully created the ".disable_magisk" file using "TWRP" and executed the "unshare" command with "SU" privileges. Unfortunately, the "last_kmesg" file was not found under "proc".
unshare -m $(magisk --path)/.magisk/busybox/sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh result:https://dpaste.org/3Gt4w
Send full, pls
dmesg:https://dpaste.org/SiWBK
Now send me /proc/mounts
/proc/mount : https://dpaste.org/pWJaB dmesg -T full : https://dpaste.org/Aupmp
Why send /proc/mounts
from Recovery??????????????
Why send
/proc/mounts
from Recovery??????????????
My fault :https://dpaste.org/NixBY
My Xiaomi Mi Pad 5 pro, the original MIUI14 Android 13, using your module version 1.18, the storage space will be shown as twice, now with the 2.1 version, it will not be
Try this magisk-overlayfs-release-7.zip
If there is bootloop, send /cache/overlayfs.log
Try this magisk-overlayfs-release-7.zip
If there is bootloop, send
/cache/overlayfs.log
this works,it is amazing!
should i close this issue right now?
Yes, you can
Yes, you can
Many thanks!
Btw you should check if it works
Btw you should check if it works
Yes,with your help,a new Adreno GPU Driver module runs very well
help me try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091028318
help me try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091028318
this version works on my device, gpu driver module
help me try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091028318
this version works on my device
Can you send /cache/overlayfs.log
?
help me try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091028318
this version works on my device
Can you send
/cache/overlayfs.log
?
oneplus 9 lineageos 20 Android 13:https://dpaste.org/kWyjD
Seem fail
help me try with this https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091028318
this version works on my device
Can you send
/cache/overlayfs.log
?oneplus 9 lineageos 20 Android 13:https://dpaste.org/kWyjD
Mi Pad 5 pro MIUI14 Android13 : https://dpaste.org/DNORi
I just tried it without your module and found that the GPU driver module works as well
https://github.com/HuskyDG/magisk_overlayfs/actions/runs/4091831635
oneplus 9 Lineageos20 Android13 : https://dpaste.org/E2wyd
After flashing this version,my oneplus 9 with lineageos20 can not boot normally,the screen shows qualcomm crashdump mode。
After flashing this version,my oneplus 9 with lineageos20 can not boot normally,the screen shows qualcomm crashdump mode。
Send /cache/overlayfs.log
After flashing this version,my oneplus 9 with lineageos20 can not boot normally,the screen shows qualcomm crashdump mode。
Send
/cache/overlayfs.log
it contains nothing,boot after create“.disable_magisk”,dmesg:https://dpaste.org/BaHi9
After flashing this version,my oneplus 9 with lineageos20 can not boot normally,the screen shows qualcomm crashdump mode。
Send
/cache/overlayfs.log
it contains nothing,boot after creat“.disable_magisk”
Or execute this command (type su first):
magiskhide exec sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh
This will process in isolated mount namespace and no Magisk and it will not damage the global mounts
Tell me the result.
magiskhide exec sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh
OnePlus9:/ # su OnePlus9:/ # magiskhide exec sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh /data/adb/modules/magisk_overlayfs/post-fs-data.sh[39]: magisk: inaccessible or not found mount: tmpfs -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx mount: overlay -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/system [lowerdir=/system,upperdir=/mnt/overlay_system/upper/system,workdir=/mnt/overlay_system/worker/system] mount: overlay -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/system_ext [lowerdir=/system_ext,upperdir=/mnt/overlay_system/upper/system_ext,workdir=/mnt/overlay_system/worker/system_ext] mount: overlay -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/product [lowerdir=/product,upperdir=/mnt/overlay_system/upper/product,workdir=/mnt/overlay_system/worker/product] mount: overlay -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor [lowerdir=/vendor,upperdir=/mnt/overlay_system/upper/vendor,workdir=/mnt/overlay_system/worker/vendor] mount: /vendor/firmware_mnt -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/firmware_mnt mount: overlay -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/dsp [lowerdir=/vendor/dsp,upperdir=/mnt/overlay_system/upper/vendor/dsp,workdir=/mnt/overlay_system/worker/vendor/dsp] mount: /vendor/bt_firmware -> /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/bt_firmware mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/system -> /system mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/system_ext -> /system_ext mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/product -> /product mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor -> /vendor mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/firmware_mnt -> /vendor/firmware_mnt mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/dsp -> /vendor/dsp mount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx/vendor/bt_firmware -> /vendor/bt_firmware mount done! clean up umount: /mnt/overlayfs_wvnnmyolkajnzpcdxmyx
@Y-ZD-heheka send /cache/overlayfs.log
?
@Y-ZD-heheka send
/cache/overlayfs.log
?
What does it say after this: (su first)
mkdir /mnt/test
mount -o rw,loop /dev/block/loop31 /mnt/test
ls -lZ /mnt/test/upper/system
ls -lZ /mnt/test/upper/vendor
ls -lZ /mnt/test/upper/product
ls -lZ /mnt/test/upper/system_ext
ls -lZd /mnt/test/upper/system
ls -lZd /mnt/test/upper/vendor
ls -lZd /mnt/test/upper/product
ls -lZd /mnt/test/upper/system_ext
What does it say after this: (su first)
mkdir /mnt/test mount -o rw,loop /dev/block/loop31 /mnt/test ls -lZ /mnt/test/upper/system ls -lZ /mnt/test/upper/vendor ls -lZ /mnt/test/upper/product ls -lZ /mnt/test/upper/system_ext ls -lZd /mnt/test/upper/system ls -lZd /mnt/test/upper/vendor ls -lZd /mnt/test/upper/product ls -lZd /mnt/test/upper/system_ext
OnePlus9:/ # su OnePlus9:/ # mkdir /mnt/test -o rw,loop /dev/block/loop31 /mnt/test ls -lZ /mnt/test/upper/system ls -lZ /mnt/test/upper/vendor ls -lZ /mnt/test/upper/product ls -lZ /mnt/test/upper/system_ext ls -lZd /mnt/test/upper/system ls -lZd /mnt/test/upper/vendor ls -lZd /mnt/test/upper/product ls -lZd /mnt/test/upper/system_extmkdir: '/mnt/test': File exists 1|OnePlus9:/ # mount -o rw,loop /dev/block/loop31 /mnt/test mount: '/dev/block/loop31'->'/mnt/test': I/O error 1|OnePlus9:/ # ls -lZ /mnt/test/upper/system ls: /mnt/test/upper/system: No such file or directory 1|OnePlus9:/ # ls -lZ /mnt/test/upper/vendor ls: /mnt/test/upper/vendor: No such file or directory 1|OnePlus9:/ # ls -lZ /mnt/test/upper/product ls: /mnt/test/upper/product: No such file or directory 1|OnePlus9:/ # ls -lZ /mnt/test/upper/system_ext ls: /mnt/test/upper/system_ext: No such file or directory 1|OnePlus9:/ # ls -lZd /mnt/test/upper/system ls: /mnt/test/upper/system: No such file or directory 1|OnePlus9:/ # ls -lZd /mnt/test/upper/vendor ls: /mnt/test/upper/vendor: No such file or directory 1|OnePlus9:/ # ls -lZd /mnt/test/upper/product ls: /mnt/test/upper/product: No such file or directory 1|OnePlus9:/ # ls -lZd /mnt/test/upper/system_ext ls: /mnt/test/upper/system_ext: No such file or directory 1|OnePlus9:/ #
After flashing magisk_overlayfs,my oneplus 9 with lineageos20 can not boot normally,the screen shows qualcomm crashdump mode。 Then i reflash boot and lineageos20,it can boot(without magisk),but when i reflash magisk in recovery mode,it boot into qualcomm crashdump mode again。