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.Supposidely, next Stable will be 22200, hence higher than Canary 2210xWent to Canary to solve the API issue.
App shows I'm running 22104 and that I'm on the Stable update channel.
Will Magisk just install the stable when the next stable update is released?
Am I right to assume this is a Ramdisk = no device, and you have Magisk in Recovery (Magisk patched Recovery image)?hi all!
Do you know if it is possible to configure something to make the Samsung Note 10 boot straight into magisk mode? (N970F variant)
The new UI3 makes it a pain in the a** to boot into magisk because you have to plug the phone into the usb.
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recoveryFor these devices, you will have to reboot to recovery every time you want Magisk...
As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk.
https://www.thecustomdroid.com/boot-samsung-galaxy-note-10-plus-recovery-download-mode-guide/- Press and hold the Volume Up and Power buttons together to boot your Galaxy Note 10/Note 10+ into Recovery Mode.
- The phone will vibrate and enter the stock recovery mode. You can release the buttons now.
I have no experience with rooted Samsung, but if you have SAR = Yes device, John's Installation Instruction, Samsung (SAR), Additional Notes will apply:Please help. My phone is bootloop, when I flash it with Odin it fails and it says sw rev check fail bootloader device -1. Please help which firmware should I use? Does firmware -1 exist?
https://topjohnwu.github.io/Magisk/install.html#additional-notes- Never, ever try to restore either boot or recovery partitions back to stock! You can easily brick your device by doing so, and the only way out is to do a full Odin restore with data wipe.
- To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always pre-patch AP in the Magisk app before flashing in Odin.
- Use HOME_CSC to preserve your data when doing a firmware upgrade in the future. Using CSC is only necessary for the initial Magisk installation.
- Never just flash only AP, or else Odin can shrink your /data filesystem. Flash full AP + BL + CP + HOME_CSC when upgrading.
Thanks, this solved my problem yesterdayLatest Debug (Canary)
Changelog and Release Notes
https://github.com/topjohnwu/magisk-files/blob/ea57c9b33b3a6ce2e0e65ce4c33dfb1c01552fcb/notes.md :
Magisk (f49966d8) (22103)
- [App] Update snet extension. This fixes SafetyNet API errors.
- [App] Fix a bug in the stub app that causes APK installation to fail
- [General] Fix a C++ bug that causes undefined behavior
- [MagiskHide] Update package and process name validation logic
Diffs to v22.1
- [General] Remove all pre Android 5.0 support
- [MagiskPolicy] Remove unnecessary sepolicy rules
- [App] Update snet extension. This fixes SafetyNet API errors.
- [App] Fix a bug in the stub app that causes APK installation to fail
- [General] Fix a C++ bug that causes undefined behavior
- [MagiskHide] Update package and process name validation logic
...And things are all Rosy 'n Safe in the Custom Mod. world once again... but ironically, only on the bleeding edge... (Confirmed on my RN8T.
)
News for those not wanting to get cut (Public Stable / Beta users) below.
Thanks John... And other collaborators for additional fixes! PW
Unhide Magisk -> install Magisk Canary from GitHub -> rehide Magisk -> restartI'm on oos11 and today I got an API error in the magisk. Any ideas ?