same result with 20.4 and latest canary. Your data will PROBABLY be preserved, however there is every chance that something may go wrong, so do a backup. Press the “UPDATE” button next to ‘Magisk Update Available!’. [ 7.684271,4] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/platform/soc/7824900.sdhci/by-name/system However, there are no magisk.log, su, or any magisk related stuff in either /sbin or /data that is installed in the device itself. If a recent version of TWRP (3.2.x or higher) isn't available for your device, it is possible to root with Magisk by patching your boot image. Continued from #3040 Magisk patches boot.img. Why GitHub? I've been watching some vids on how to install magisk and followed along with the tutorial. It's the same as if it were stock, no changes at all. If I can't get Magisk working, how does SuperSU work? Patching the boot image manually and flashing it causes panic and reboot to bootloader. In MagiskManager select Uninstall > Complete Uninstall. Now I have to use the "temporary" TWRP to do my ZIP flashing. It worked once, now it gives me two flashes and loops until I head back to Fastboot. [ 7.670957,4] init: Using Android DT directory /proc/device-tree/firmware/android/ I tried restoring from the TWRP backup and reflashing the permanent TWRP, nope, still looping. I'm flashing to stock, restoring from TWRP, and starting over. I can not, for the life of me, figure out why Magisk is not installed even when the process goes seemingly perfectly. Select “Install” and then press “Direct Install” to install the Magisk 20.4 update on your device. they're used to log you in. Best place for anything to do with phones are the XDA forums. The log is as attached below. Press question mark to learn the rest of the keyboard shortcuts. I haven't a clue, I'm new to this. Successfully merging a pull request may close this issue. privacy statement. it don't really resolve the issue but a workaround I found : with a custom kernel it work, I'm using sphynx kernel but it should work with any other. So I was to try flash it again. Also (probably unrelated but worth a mention), our prop getprop ro.build.system_root_image is set as false and if set to true gives an obvious bootloop because we are not using the legacy system-as-root implementation. Reboot to recovery and flash Magisk zip (at the time of writing this was 20.1). kernel tree : https://github.com/ArrowOS-Devices/android_kernel_motorola_sanders And logcat has not a single line about magisk.init. You can always update your selection by clicking Cookie Preferences at the bottom of the page. Use a computer, connect the device and use ADB to catch a logcat from boot up until you can confirm that Magisk reports "not installed" (How to logcat). You signed in with another tab or window. Do you have Magisk Manager hidden but then opened the unhidden version installed by the TWRP flash instead? But rebooting to system showing Magisk isn't installed. If … Learn more. The following worked for me. Try downloading the official system image from oneplus.com, move the file to your root directory (/sdcard), then go to Options > System > System Updates > click the gear icon > Local Upgrade. I also experienced issues with Magisk, although in my case the Manager reported it as installed and up-to-date but only one app asked for access to su and everything else was denied. I flashed my G7 Plus with LineageOS 16 (Unofficial) read the thread very carefully about how to install TWRP to both slots so it is installed on your phone and follow the instructions to the letter. Log shows complete. Learn more, We use analytics cookies to understand how you use our websites so we can make them better, e.g. I also experienced issues with Magisk, although in my case the Manager reported it as installed and up-to-date but only one app asked for access to su and everything else was denied. Magisk 16.7 also seems vulnerable to the bugs herein presented, I experienced them but I can't remember the circumstances very well, except that if install it on Motorola's stock oreo 8.1 I will experience this bug after a while. Previous similar issue with devices on android 11 and boot.img has no 'apex' dir. We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products. We’ll occasionally send you account related emails. I did think it was weird that the Magisk modified boot.img was smaller than the stock boot.img. Reboot to recovery and flash MagiskUinstaller.zip. Click on Install and then select Patch Boot Image File if you have Magisk Zip file. MagiskUninstaller.zip won't flash. But booting TWRP is failed. Catch-22. do not think oversized image is the issue . Every single time I try to install Magisk and then start the Magisk Manager, it says Magisk is not installed, even though I just installed it, both with TWRP and manually. recovery.log We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products. Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world. hello, my issue was resolved with a clean flash of my rom, by wiping /data. installation failed. Just for a little more clarification for the issue, flashing the magisk zip does patch the bootimage. A magisk folder is also created in the /data/adb path and a.magisk file is also present in the /data path. https://github.com/ArrowOS-Devices/android_device_motorola_sanders, https://github.com/ArrowOS-Devices/android_kernel_motorola_sanders. It worked once, now it gives me two flashes and loops until I head back to Fastboot. Now after installation Reboot the system and then open Magisk Manager. logs here as well !! I just tried it and it seems there's a little progress there. My phone is boot loader unlocked officially through Motorola. Code review; Project management; Integrations; Actions; Packages; Security no i don't have any file like magisk.log in storage. 9 posts Thanks Meter: 1 . By clicking “Sign up for GitHub”, you agree to our terms of service and as to the size of the boot.img. We use essential cookies to perform essential website functions, e.g. To be concluded: Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Reboot to recovery and flash MagiskUinstaller.zip. It means that you need to Install Magisk Zip file. Flashing the Magisk zip using TWRP is success. My phone is a T-Mobile Revvlry (rebranded G7 Play) running Android 9 I've been trying for hours to figure out why I can't get Magisk installed and my phone rooted, and I still can't figure it out. Magisk is not installed. it can download the file no problem. Is the Magisk modified boot.img supposed to be smaller than the standard boot.img? Every single time I try to install Magisk and then start the Magisk Manager, it says Magisk is not installed, even though I just installed it, both with TWRP and manually. I just want to root my phone. Extracting the ramdisk shows that a.backup folder is created with the magiskinit as well as the system init. Once finished, press the “Reboot” button. In recovery mode, select the Install button. Already on GitHub? Then flash magisk from twrp, New comments cannot be posted and votes cannot be cast. I tried wiping Dalvik, didn't change much. Select the zip file; Swipe the slider to install Magisk; Tap Reboot System; 3. dmesg.log, device tree : https://github.com/ArrowOS-Devices/android_device_motorola_sanders [ 7.669484,4] init: init first stage started! Although, side note (not sure if it is relevant or not), the fstab in our /vendor/etc doesnt seem to be affected at all after flashing the zip but I'm not sure if it would be visible after boot so I might be a little off here. Still the same. Page 1 of 2 1 2. Press J to jump to the feed. A magisk folder is also created in the /data/adb path and a .magisk file is also present in the /data path. It ended up booting to system. Magisk 16.0 seems unaffected by the root loss or magisk not installed bug, but I had instances where the download section would not show up. Magisk 16.0 seems unaffected by the root loss or magisk not installed bug, but I had instances where the download section would not show up. Non-SAR build/TWRP direct install fails after downloading the zip saying unable to check signature. recovery and dmesg logs Features →. Looking in the \data\ files, parts of magisk are there, and some things detect MagiskSU, but magisk.img is always missing. the rom (xiaomi eu) was on beta so it surely break something when updating to Android Q. Hi, this issue has now been solved. From your description you don't appear to have wiped Dalvik/cache. In MagiskManager select Uninstall > Complete Uninstall. Find the folder where you download the zip file. Switching to the source dtbtool and reverting a few old commits helped to do the trick. Now I have to use the "temporary" TWRP to do my ZIP flashing. Magisk: 20.3 Downloaded the Magisk.zip file through Magisk manager. [ 7.671795,4] init: [libfs_mgr]ReadDefaultFstab(): failed to find device default fstab The problem was in our custom motorola dtbtool that wasn't properly oriented towards creating the proper boot image of Android 10 for the Magisk zip to be able to patch the fstab.