Ok then, successfull update on 3 out of 4 my devicesRight. Didnt try update on the watch yet.
Ok then, successfull update on 3 out of 4 my devicesRight. Didnt try update on the watch yet.
Actually I couldn't boot into recovery. Only fastboot was working so I flashed all partitions using fastboot zip stock rom but I do not recommend that as you will get everything wiped. Now I would try flashing just stock boot.img in fastboot and then boot into recovery to flash rom. This way I wouldn't wipe everything...
@Newtype14Hoping someone can help me, my phone is stuck at the Samsung boot logo after updating Magisk.
At that point, I realized something had gone wrong, and since I didn't care about losing all my data, I did a force reboot into TWRP and did the following:
Formatted Data.
Wiped Dalvik, System, Data and Cache.
Restored a Nandroid backup that I had made before rooting my phone.
Once I did all that, I rebooted and the phone is still stuck at the boot logo. How is that possible?
@Newtype14
Would you mind telling me a couple of things:
have you flashed TWRP after complete magisk set-up ?
how did you do the Nandroid backup before rooting? have you used an app?
Thanks
...I did a force reboot into TWRP and did the following:
Formatted Data.
Wiped Dalvik, System, Data and Cache.
Restored a Nandroid backup that I had made before rooting my phone.
Once I did all that, I rebooted and the phone is still stuck at the boot logo. How is that possible?
Samsung Galaxy S7 (SM-G930W8)
Android 8.0 Oreo
I flashed TWRP before doing anything with Magisk, then booted into Recovery mode and in TWRP, I created a backup by selecting: "Boot", "System", "Cache", "Baseband" and "EFS".
For additional information: I did wipe my phone three weeks ago and used that backup to restore and it worked fine.
Well, you just need to understand that being systemless, actual Magisk is flashed to boot image (assuming ramdisk [in boot image] = yes), so this is what got corrupted by bad flash.All I see is boot.emmc. This backup was done before rooting with Magisk.
View attachment 5231743
Not sure I understand what I should try doing. I don't have much experience since I just recently learned how to root.
The reverse is also true: to remove Magisk root (or corrupted Installation), simply flash back UNPATCHED boot image (download and extract from your current ROM package).
Serious issues with v22 update - MagiskManager shows the new Manager ver as being v. 22 I didn't see any changelogs, so I selected Updatefor Manager app (not Magisk) from MagiskManager - so v22 became the Manager version and Manager showed no Magisk or root, and all crapped out. Using old Xperia Z3 but running Android 10 - CarbonRom (Lineage variant, very nice btw)
Solution: First I downloaded older version of Magisk 21.4, latest Magisk uninstaller, and Manager 8.0.7 Second, unininstalled MagiskManager v22 app. Third reboot to TWRP and uninstalled Magisk with latest Magisk uninstaller. No reboot, directly installed Magisk v 21.4 from TWRP, booted to system, and installed apk for Manager v 8.0.7 and all runs fine - have root.
New development - Manager keeps "Checking for updates . . ." and not showing version installed or available. Guess the Magisk Team is on it. Now shows Manager is up to date.
You 're right . But Magisk was included in my Custom Pie ROM I've used for 2 years. Until r22 I didn't know that a file magisk.apk was into my system/app folder. Until r21.4 , all the updates didn't detect it. Now everything is back to the normal and it is running fine. Finally not a big issue. Thanks for your help.It is known issue that Magisk Manager (now Magisk app) must not be installed as a system app (also not on external SD).
AFAIK, documented somewhere in Magisk docs or Wiki, it was also discussed here and under Github issues
The Manager is still showing an update for itself (22.0) but that can't be right. I think the repo URLs might have gotten mixed up or something.
Issues on MIUI Global 12.0.3.0(QFGEUXM) (Redmi Note 7 - Lavender), Android 10 QKQ1.190910.002
Magisk v22.0 doesn't work at all, seems to patch fine in TWRP, but boot stucks at MIUI logo, hangs there for a while, then reboots to recovery (TWRP 3.5.0_9.0-lavender).
Tried installing through patching and flashing stock boot image and recovery (one at a time), but none of these have worked.
I was able to install Magisk v19.0 (TWRP zip flash) and boot, but Magisk Manager nor Magisk app won't detect it (if I try to flash zip again it says "Detected magisk patched boot image" (or sth like that) and patches fine).
Any solutions?
Someone confirm that issue tracker of Magisk is there or not.
I cannot able to see it in repo.
John got fed up with the spamming of low quality issue reports...
You are The Messiah good sir! Thank you, thank you so much. For almost everyone stuck with acquiring the boot.img file, if you are using any custom ROM, check its ZIP, it will have a boot.img file within it without fail. Simply flash it usingMay I ask what those devices are exactly & the method you used?
***
fastboot flash boot boot.img
and you're good to go.Magisk itself is not Systemlesss, in that it modifies the BOOT partition, which some would cal a "system" modification. However, technically NOT touching the SYSTEM partition.i previously asked that too "why is magisk called systemless when it's capable corrupting system partition" but nobody answered me i guess it's one of those question like
Which Came First, the Chicken or the Egg?
nobody know thou it's better left unanswered
That could be the case, but if yur boot partition is corrupted (ie not working) then there would be no chance for your phone to work exactly; booot gets loaded before system). But also (as you stated), if the Magisk install starts making "bad" changes to tour system, then the system wont boot / operate correctly. The first step to recover from such a situation is commonly to flash back the original boot image (doing so is built into magisk), and hence remove the system changes and hopefully that will give you a working system. Or remove all your modules (ie systemless changes)that make sense so if magisk installation got corrupted then system partion would appear to be corrupted to since magisk is symlinking or like emulating system partition
Little confusing what you now have; what does Magisk app report under Magisk, Installed, and under App, Installed respectively?On clean flashed (fully wiped) LineageOS 18.1, Xiaomi Mi A1, v22.1, the app didn't work initially after flashing the apk renamed as .zip (it threw an error message trying to download and install the full app after tapping it in the app drawer). I then manually installed the app by using the normal apk. Everything works fine su wise but attempting to install a module crashes the app, event though notifs say it's downloading (but doesn't install).
Yes, of course!It's systemless because it doesn't modify the system partition by default.
Not sure this matters much once AVB is defeated by unlocking bootloader, but since most newer stock ROMs are locked to read-only due to 'Shared Blocks' implementation, a systemless solution may be the only practical option.Android checks the partition integrity at boot on most new devices.
Well, it exists always in a boot image certainly, as it's always in ramdisk. But recovery image is also a boot image with ramdisk!It didn't in the earlier versions of Android. You could literally just add root permissions right to the system and have no problems. Since that is no longer the case, it now resides in the boot image, not system image and never the recovery image.
In the case of type III devices, Magisk in Recovery is the only option for Magisk root. Please see Magisk in Recovery section in Installation Instructions:recovery and boot partition:
these 2 are actually very similar: both are Android boot images containing ramdisk and Linux kernel (plus some other stuff).
Looks like you have /dev/bootimg as your real partition location and it is still higher in the list in util_functions.sh like how I fixed it in the linked commit, so this is definitely a regression from some other recent change to Magisk.. sigh, I'll look into it.@osm0sis
Thank you for having an eye on that.
Did the "ls" twice, first from a TWRP-terminal in recovery, second from a terminal while phone is "up and running".
No, the phone is an Estar Takee1.
ROM is from here: Mikel Android 7 for Takee1
and is itself a port from this ROM: RidonOS for Micromaxx A311
You're right, sorry for that. Now here the installation log for canary-version:
- Target image: /dev/BOOT
- Device platform: armeabi-v7a
- Installing: f152b4c2 (22005)
nanddump: MEMGETINFO: Not a typewriter
Parsing boot image: [boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
That was quick... Didn't even have to whisper your name three times in the mirror.
Boot image is here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84688655
And this is supposedly the install log:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84686805
And for good measure there's a Magisk log as well:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84695083
And some device info:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84689305