Related
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.
I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.
Thanks. Guess this works.
Can you please elaborate?
dunderball said:
I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.
Click to expand...
Click to collapse
Hi,
Can you please elaborate the steps. Sorry, I'm a noob. Where to create a new folder? How to set the permissions on it? to rwxr-xr-x ?
Thanks.
Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.
Thanks for the quick response but..
Didgeridoohan said:
Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.
Click to expand...
Click to collapse
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk.
Code:
02-14 15:51:58.289 437 437 I Magisk : Magisk v16.0(1600) daemon started
02-14 15:51:58.298 437 442 I Magisk : ** post-fs mode running
02-14 15:52:01.565 437 682 I Magisk : ** post-fs-data mode running
02-14 21:22:01.571 437 682 I Magisk : * Creating /sbin overlay
02-14 21:22:01.572 437 682 I Magisk : * Mounting mirrors
02-14 21:22:01.573 437 682 I Magisk : mount: /sbin/.core/mirror/system
02-14 21:22:01.573 437 682 I Magisk : link: /sbin/.core/mirror/vendor
02-14 21:22:01.574 437 682 I Magisk : bind_mount: /sbin/.core/mirror/bin
02-14 21:22:01.574 437 682 I Magisk : * Setting up internal busybox
02-14 21:22:01.586 437 682 I Magisk : * Mounting /data/adb/magisk.img
02-14 21:22:01.598 437 682 E Magisk : mount /dev/block/loop0->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.598 437 682 E Magisk : umount /sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.608 437 682 I Magisk : Resize /data/adb/magisk.img to -1854921600M
02-14 21:22:01.637 437 682 I Magisk : Create /data/adb/tmp.img with size -1854921600M
02-14 21:22:01.660 437 682 E Magisk : mount /dev/block/loop0->/dev/source failed with 22: Invalid argument
02-14 21:22:01.670 437 682 E Magisk : mount /dev/block/loop1->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.670 437 682 I Magisk : * Running post-fs-data.d scripts
02-14 21:22:01.671 437 682 I Magisk : * Running module post-fs-data scripts
02-14 21:22:01.671 437 682 I Magisk : * Loading modules
02-14 21:22:01.671 437 695 I Magisk : * Starting MagiskHide
02-14 21:22:01.671 437 695 I Magisk : hide_utils: Hiding sensitive props
02-14 21:22:01.671 437 695 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
02-14 21:22:01.671 437 695 I Magisk : hide_list add: [com.google.android.gms.unstable]
02-14 21:22:01.691 437 695 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-14 21:22:01.813 437 755 I Magisk : ** late_start service mode running
02-14 21:22:01.814 437 755 I Magisk : * Running service.d scripts
02-14 21:22:01.814 437 755 I Magisk : * Running module service scripts
02-14 21:22:03.538 437 695 I Magisk : proc_monitor: zygote ns=mnt:[4026533676] zygote64 ns=mnt:[4026533675]
03-06 12:56:00.383 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4625 ns=mnt:[4026533848])
03-06 12:56:24.289 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6244 ns=mnt:[4026533862])
sghegde87 said:
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk
Click to expand...
Click to collapse
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?
Yes you are right.
Didgeridoohan said:
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?
Click to expand...
Click to collapse
Yep. It's a mount issue. The problem was F2FS data partition. I formatted it to EXT4 and everything is working just fine. Magisk works as expected only on EXT4 format type in Lenovo P2 stock ROM.
Thanks for the comment though!
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
hidelist deleted
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks
jhford said:
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks
Click to expand...
Click to collapse
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).
Didgeridoohan said:
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).
Click to expand...
Click to collapse
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks
jhford said:
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks
Click to expand...
Click to collapse
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Didgeridoohan said:
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Click to expand...
Click to collapse
My Magisk log is attached.
jhford said:
My Magisk log is attached.
Click to expand...
Click to collapse
Update. I uninstalled Magisk manager and installed the Canary version, but the problem remains. Neither Safetynet nor Magisk Hide work unless I do the following: disable Magisk Hide, reboot, and enable Magisk Hide. I'm glad it works, at least, but the rebooting is a PITA.
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.
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Clear Magisk Hide List.
- In-Case Of Facing A Bootloop Issue Due To Adding App/Activity/Process To Magisk Hide, Flash This Module
- This Module Clears All Added Apps/Activities/Processes In Magisk Hide List
- After The Installation & Booting, It Clears Magisk Hide List & Disables Itself
- Enabling This Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearHideList
- For Activating The Functionality Of ClearHideList, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideList --> Delete The File Of Disable From The Folder Of Active --> Reboot
- For Using The Module Thru ADB Shell/TWRP Terminal [The Module Must Be Pre-Installed Via Magisk Manager/TWRP Recovery/ADB Sideload], Write The Following Commands --> rm -f /data/DreamerMods/MultiFunctions/MagiskHideList/Active/disable (Click On Enter) --> reboot (Click On Enter)
Created: Oct.01.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Flash It Thru TWRP Recovery
- Or Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
Reserved for News/Updates #2
This module is useful! THANKS!
Updated ClearHideList4Magisk To v1.0.0A!
Changelog: Checking The Paths
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v17.2(17200)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To The Latest Version Which Is Currently v17.2(17200)
Updated ClearAll4Magisk To 1.0.3.0A!
Changelog: Rewriting The Script & Adding Extra Options
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Kindly Be Informed That
- For Doing Its Functionality, Use Any File Explorer --> Internal Storage --> DreamerMods --> The Module --> Delete The File Of Disable From The Folder Of ClearMagiskHideList --> Reboot
Updated MultiFunctions4Magisk To 1.0.3.3!
Changelog: ClearHideList Is A Sub-Module Of The Main Module Of MultiFunctions Which Supports Currently The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode & Opening Magisk In Core Only Mode]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Kindly Be Informed That
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearHideList
- For Activating The Functionality Of ClearHideList, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideList --> Delete The File Of Disable From The Folder Of Active --> Reboot
Download link?
https://androidfilehost.com/?w=files&flid=293646 which you provided does not work. There is no file to download.
No files, dude....
amirasyraf said:
Download link?
https://androidfilehost.com/?w=files&flid=293646 which you provided does not work. There is no file to download.
Click to expand...
Click to collapse
The zip-file 'MultiFunctions4Magisk-v1.0.3.3(v19000)(3MF).zip' (being the version for Magisk V19) can be downloaded via this link:
https://androidfilehost.com/?fid=1395089523397962220
73sydney said:
No files, dude....
Click to expand...
Click to collapse
amirasyraf said:
Download link?
https://androidfilehost.com/?w=files&flid=293646 which you provided does not work. There is no file to download.
Click to expand...
Click to collapse
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Hello,
it seems like my Magisk Hide option for some reason cannot be saved, if I enable Magisk Hide and go to custom Magisk Hide app list if I select an app and refresh, the app is unselected again. Also, it seems like the Magisk Hide option in the settings menu is also not being saved. I am using Magisk 19.1 and Magisk Manager 7.1.2 because with those versions I have been the most succesful, newest version does not even show Magisk Hide specific app list menu option. Android version is 5.0.1 and I am using Samsung Galaxy S4.
What could be wrong here? I can provide any additional information needed.
That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...
Didgeridoohan said:
That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...
Click to expand...
Click to collapse
Thanks so much I've been looking for answer for 2 full days I hope this works!
I have installed v20.0, but now when I select Magisk Hide it does not even show Magisk Hide menu option to select specific apps. What could be the problem?
No need to open another thread... We can continue the discussion here.
If you post your Magisk log it might be easier to help.
Didgeridoohan said:
If you post your Magisk log it might be easier to help.
Click to expand...
Click to collapse
How to get Magisk log?
Here is the log:
--------- beginning of system
--------- beginning of main
I/Magisk ( 280): Magisk v20.0(20000) daemon started
I/Magisk ( 280): * Device API level: 21
I/Magisk ( 280): ** post-fs-data mode running
I/Magisk ( 280): * Initializing Magisk environment
I/Magisk ( 280): * Mounting mirrors
I/Magisk ( 280): mount: /sbin/.magisk/mirror/system
I/Magisk ( 280): mount: /sbin/.magisk/mirror/data
I/Magisk ( 280): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 280): * Setting up internal busybox
I/Magisk ( 280): * Running post-fs-data.d scripts
I/Magisk ( 280): ** late_start service mode running
I/Magisk ( 280): * Running service.d scripts
I/Magisk ( 280): ** boot_complete triggered
If you could install the current Canary debug build and provide that log it would be great. First, there's really no support for old releases and the Canary debug logs are much more verbose.
Canary builds can be found here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
I am using Canary build now, but when I go to logs, it says that the log is empty.