yashsingh1/xdaforums huggingface dataset:
[Magisk] stormy1777:
Thanks for the tips, and time writing.

@pndwal thanks for the time, tips. helped.

Finally managed to update to magisk v22, with help of an EXTERNAL patcher:

GitHub - YaAlex3/patcher-oss: ARM32 zImage Patcher

ARM32 zImage Patcher. Contribute to YaAlex3/patcher-oss development by creating an account on GitHub.

github.com

It appears there's something "funky" with Redmi 7A in that ramdisk=no, but if patched outside by such tools, it can be added back, then Magisk's patching works.. original thread above has exact steps I've carried out.

Thanks.

Stormy.
[Magisk] proza:
The ROM that I would like to install Magisk to is a custom ROM, but I have no intention of modifying the partition that are protected by dm-verity such as system.img and vendor.img, so I should leave "preserve avb 2.0/dm-verity" unchecked?
[Magisk] maquille:
Hi everyone, I have a huge problem. My S10e is stuck on download mode after restoring the magisk application via titanium backup.

Let me explain: I wanted to update magisk via the magisk interface. I downloaded and installed the new magisk but decided to go back to the old version.

I did it with titanium backup and restored the old magisk version. Everything seemed to be fine, because I had found the old interface.

I then restarted my phone and the I got stuck on the Dowload screen.

ODIN MODE (DT Load Fail)

[DTH] dt table headet check Fail <unknown error>

Load_kernel: could not do Normal boot. (DT LOAD Fail)

vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)

vbmeta: VERIFICATION_DISABLED bit is set.

CUSTOM VBMETA

VBMETA: No sign info

VBMETA

The problem is, I didn't back up my system before doing this.

I know I mistaked reinstalling magisk via titanium.

Would you have any chance a solution to my problem, without losing the data of my rom?

Thank you so much.
[Magisk] pndwal:
Great.

But Magisk in boot image working on R7A (ramdisk = no) is NOT funky for Xiaomi.

As I mentioned, this in fact works on ALL OTHER type III Xiaomi devices I know of, simply because despite having no factory ramdisk (which Magisk assumes indicates bootloader will be incompatible w/ boot partition ramdisk), Xiaomi in fact leave this legacy ramdisk support in bootloader, so Magisk does load if boot image is patched with Magisk AS WELL as basic ramdisk components.

John Wu in fact acknowledges this, and has added the manual ramdisk patching also to allow it to work natively in these cases (ramdisk = no remains, and is still a true indicator of FACTORY ramdisk state), and it does, in fact, normally work fine. See last paragraph of this doc:

https://topjohnwu.github.io/Magisk/boot.html

So, if missing, ramdisk is in fact ALWAYS added to boot image when patched by Magisk app. It just won't work unless boot partition ramdisk support (inexplicably in the case of type III devices) exists in bootloader.

What does seem 'funky' is that Magisk's native manual ramdisk patching function hasn't worked for you w/ R7A, while 3rd party manual patching has. PW
[Magisk] Raptor270:
Hi,

I installed the new magisk update through magisk and since then my Xiaomi Mi Mix 3 keeps random rebooting.

Any idea whats causing this?

Thanks for your help
[Magisk] Didgeridoohan:
Guessing is difficult... Logs make it much easier:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] pndwal:
Announced:

PW
[Magisk] aryanhington:
please can you advise how to make changes to vendor/build.prop with magisk installed as there is also sbin/.magisk/mirror/vendor/build.prop, editing vendor/build.prop does change the values and saves but does not reflect any changes in terms of functionality?
[Magisk] jeffghh:
hi guys, which magsik version can i use to root galaxy s7 edge exynos?
[Magisk] Spartacus500:
Upload this version via TWRP, then update to the latest one
[Magisk] DiamondJohn:
I didnt read if it was covered in Didgeridoohan 's link,but my normal first port of call for a random reboot or bootlook is the last_kmsg
[Magisk] aryanhington:
does anybody know when should /sbin/.magisk/config have keepverity and forceencryption disabled and when should it be enabled?
[Magisk] ineedroot69:
what are you doing? why you manually changing them?

anyway here's what they does from the god himself John Wu

preserve avb 2.0/dm-verity

Preserve force encryption​
[Magisk] me_droid:
Anyone taken the plunge on 22.1, updating within the app by just pressing the update button? TJW refers us to the release notes for 22.0 so assume we have to unhide magisk again?
[Magisk] ineedroot69:
this is full changelog for 22.1 https://topjohnwu.github.io/Magisk/releases/22100.html i guess thats the case i'm still using my phone for "important stuff"😌 (totally not porm related) so i didn't get updated yet to the latest version also would be troublesome to experience bootloop again
[Magisk] pndwal:
Yes, updates fine! ... But I didn't try w/ app hidden.

Those notes were for coming from incompatible 21.4 etc. I assume unhiding is not necessary coming from 22.0 w/ new hiding protocol. Someone may confirm. PW
[Magisk] pndwal:
Latest Debug (Canary)​

Changelog and Release Notes:​

Magisk (e136fb3a) (22102)​

[General] Remove all pre Android 5.0 support

[MagiskPolicy] Remove unnecessary sepolicy rules

Diffs to v22.1​

[General] Remove all pre Android 5.0 support

[MagiskPolicy] Remove unnecessary sepolicy rules

👍 PW
[Magisk] Didgeridoohan:
Why not use v22.1 directly? Or is there some known incompatibility with the S7 Edge?

And also, why not link directly to the files on John's Github? Always the safest way...
[Magisk] Didgeridoohan:
For future reference, it is covered. (y)
[Magisk] Didgeridoohan:
There's no need to unhide the app if you're already on v22+. That's only necessary when updating from older releases.
[Magisk] ineedroot69:
i been traumatized with 22.0 so can i just directly install the update without extra preparation and not expecting any issue or bootloop?
[Magisk] Riyad_:
After installing or removing a module in magisk 22.1 when click the reboot option there is a message that show formatting data instead of rebooting. and also after that the system boot itself into recovery. i can't say its a boot loop because if reboot the device by using power key it works . Also after booted into recovery ,reboot to system also works fine. anyione facing this issue ???
[Magisk] Didgeridoohan:
You should always expect and prepare for issues and bootloops, but the most of the problems we saw with the v22.0 update should have been fixed in v22.1. This entry from the changelog is my best bet on what was causing the broken boot images we saw in the last release:

I say go for it (as long as you have all your important data backed up, of course).
[Magisk] jhedfors:
Is there a replacement for the announcement thread? It hasn't been updated for a long time and I cannot find any reference to it being discontinued.
[Magisk] Didgeridoohan:
From the announcement thread:
[Magisk] ashrr:
I got a notification to update to 22.1 today, pressed it and nothing happened. Tried to open the manager app and it wouldn't open so I waited 5 minutes then rebooted to see if it would fix it but bootlooped instead. I was on the latest version before updating which I think was 22.0. I've just tried flashing 22.1 again in recovery but I'm still bootlooping. Any ideas how I can fix this?
[Magisk] ineedroot69:
what do you mean by flashing? i thought only the app receive update(which is apk and can be directly installed like any other apk)

did you just decided to download the new magisk apk and flash it instead of installing the update directly from magisk app... ohh nooo

also perhaps youre wifi connection is slow (since it's downloading the update) should've have waited longer instead of rebooting your device
[Magisk] ashrr:
Installation

The Magic Mask for Android

topjohnwu.github.io

Yh renamed the apk to zip and flashed that after the normal method failed.

I doubt it was due to a slow connection, I get about 200mb down from the room I was in. Yh I probably should've waited a bit longer but 5+ minutes is usually more than enough.
[Magisk] ineedroot69:
you have TWRP? just grab the partition Magisk backup and fastboot flash it
[Magisk] ashrr:
Yh I do. Where can I find magisk backup partition? I used to flash custom roms and kernels back when I had my Nexus 4 but these days it's just stock with magisk so I'm pretty much new to this whole thing.
[Magisk] kevk60:
Have updated to Magisk 22.0 on oneplus 6t and 8t and had no problems. Updated to Magisk 22.1 on both and have had no problems.
[Magisk] aryanhington:
anyone know if verity can be disabled by editing /sbin/.magisk/config as can't see the option of verity within magisk manager app?
[Magisk] JimSmith94:
I won't get my phone back until sometime next week. Before I build up the courage to root it again, can someone confirm that my patching the boot image after installing the April Security update but without checking for a Magisk Manager update first was what bricked my Pixel 5?
[Magisk] ashrr:
Ok I'm getting nowhere. I got the backup boot.img which I extracted from /data/magisk_backup_sha1/boot.img.gz and flashed it using the command fastboot flash boot boot.img and my OP 5T just shows a white led and ends up in some diagnostic mode. I've also tried flashing the stock boot.img then flashing magisk but that didn't work either. Does anyone want to help me with some instructions a 5 year old could follow?

I have a twrp backup from a while ago which is for the same android version but an older magisk version and I also have one with the broken boot after the failed update from 22.0 and before attempting to flash 22.1 again in twrp.

Edit: I've gotten back into android by restoring my system backup from late 2019. I then uninstalled the broken magisk app installed 22.1 again and all is working fine. I've tried restoring the broken system image but it bootlooped again. What could be causing this? The only thing I can think of is substratum.
[Magisk] ineedroot69:
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
[Magisk] DiamondJohn:
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.

The "magic" of Magisk is that after that, all modifications that appear to be to the SYSTEM partition are actual achieved by systemless mods; the mods are in the DATA partition.

Its the differentiation between BOOT and SYSTEM, and that the changes made by Magisk are systemless. Magisk is not ...errr.. "bootlesss";)
[Magisk] ineedroot69:
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
[Magisk] DiamondJohn:
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)

PS: in case you haven't already, simply report your own double post to get it removed.
[Magisk] J.Michael:
@ineedroot69 If you think you can't boot because of a Magisk module, try booting to Safe Mode. I think when you boot to Safe Mode, Magisk does not run. Then, the next time you boot, Magisk runs but does not activate any modules. At that point, you have root, so you should be able to delete or disable the modules.
[Magisk] Iron_Overheat:
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).
[Magisk] op3tguy:
First time here and I hope I'm asking this question in the right place.

Oneplus 3T running OOS 9.0.6 since about Jan. 2020 with Magisk installed a long time ago.

TWRP 3.5.2_9

This morning there was a download for Magisk which I ignored. (Little download arrow at the top of the screen.)

I was using the phone fine for a few hours until I got out of the car and put it in my pocket.

10 minutes later I noticed it was hot, took it out and found it stuck at the prompt for start/recovery/bootloader etc.

It will not complete its boot.

I can get to TWRP, I've tried flashing v22.1 but it fails in the same way.

! Unsupported/Unknown image format

- Unmounting partitions

Updater process ended with ERROR: 1

I've attached the dmesg.log and recovery.log if that helps.

I have Nandroid backups from the last time (after) I upgraded to OOS 9.0.6.

Any help would be appreciated.
[Magisk] foongwk:
TWRP 3.0.2.0 i may flash it, where do i get the file SuperSU 2.78-SR1-systemless?
[Magisk] soder:
Search for it.

/Söder
[Magisk] Hyflex:
So how do I use phh hide su with magisk?

I've currently got to stick with Android 5.1.1 because CynanogenMod 13 is triggering root check on the Sky Go app even though there is no root, busybox... After running unsu and busybox uninstall.
[Magisk] aroblu94:
Hi all, I'm having some troubles with viper4android.

Personally I've never used v4a before except for something like 3 days, but now I have Magisk v7 and I saw v4a in the modules list I wanted to try it.

Well, I installed the module from Magisk Manager end the apk founded here at xda but the app days I have to install/update drivers and from Magisk Manager the v4a module always says "Module will be updated at next reboot"

Does someone have the same problem? Thanks
[Magisk] andrew2432:
Systemless su needs MM, droid OS 6.0 I believe. I don't want that to be your issue, though v7 may say incompatible sdk when flashing in twrp.

I tried helping a friend with magiskv7, Systemless su, su hide, magisk manager 2.0 and we could not get it. Ended up letting me fash a 5.0 lollipop stock and use magiskv6. Easier for me personally
[Magisk] ChokingHazard91:
What phone do you have? And did you reboot after selecting the module?
[Magisk] topjohnwu:
I've been busy with schoolwork lately, please forgive my absence :)

For those who can't wait for the official release, you can have a sneak peak of magiskhide from Github. It has some bugs, but currently I have no time to fix it. If your module is handled by Magisk's auto-mount, then magiskhide can hide it fine.

Current magiskhide can hide phh's root and all auto-mounted Magisk modules. Known issue is that if you replace some of your framework files with Magisk, Google Play Service will crash. More bugs might be there I'm not aware of. Please use it with your own caution.

No support for magiskhide now, please don't spam the forum with magiskhide issues if you're using it
[Magisk] andrew2432:
I don't believe we did which would suck...

Only doing this for pogo haha

I use a lgg2 at&t with magisk6 on a stock de bloated 5.0 rom. Magisk manager 1.2 apk, phh su 17. It worked fine until I tried to make a pdanet tablet app work on it. I have currently set my proxy and port settings through the app and am unable to change them back. This lgg2 is unlocked with no sim, the reason I was trying pda net. Currently looking for a fix other than stocking and starting over.

For him, galaxy s5, I can't remember the carrier at the time of this writing, NOT SPRINT, look for edit later. Ota'd to MM. Wanted back because of something about SD cards not working right.

I use an s5 running magiskv6, manager 1.2, phh su 17. I did this after attempting magiskv7 and the corresponding phhsu. Uninstalled them with zips, also missed an su in the /xbin before first opening of pogo. Cant athenticate. Lg when i had internet accesed pogo servers. My s5 is on the last lollipop build for the smg900p, OK4.
[Magisk] ChokingHazard91:
I'm not sure if phh hidesu allows you to play Pokémon, I know SuperSU + suhide does. But on some devices, like my Note 4, you can't install Xposed if you have suhide installed. But suhide is only for Marshmallow so you can't install that..
[Magisk] andrew2432:
Nice on the name, seriously smart. we gotta hide it from the games devs, which are all probably members/devs/moderators on here anyway hahaha. We didn't try su and su hide while on MM. We tried Phh and its hide,maybe im stupid and tried su side with phh... i haven't been convinced an xposed works with art runtime and TouchWiz on my specific carriwr model, didnt want to try on someone elses. If it exists I'm not confident enough to try What note 4 varient? At and t locked bootloader idk how to fix for a buddy if you know anything there

I know LP+magiskv6+manager1.2+phh su works to log in and play normal. I also know the paid fakegps moved to system does what it's supposed to...which is why I used it for him and want to do it to my smg900p.
[Magisk] drmpk:
Same here. I too tired what all you tried. But ended in bootloops. At the moment we note 4 users can't get suhide and xposed work together by whatever means we know as of now. Systemless supersu + magisk + xposed work just fine. Systemless supersu + magisk + suhide works fine too.
[Magisk] srancier:
Can anyone tell me why I get an error message when trying to open the Magick Manager 2.0 apk? Says cannot open file.
[Magisk] requiiiem:
Open with solid explorer, es file etc

---------- Post added at 09:05 PM ---------- Previous post was at 08:54 PM ----------

The most recent v4a magisk work on Android 7?
[Magisk] Alxoom33:
Yes, perfectly.
[Magisk] requiiiem:
Dont work on play music app? :(
[Magisk] Warkeyx:
i know im newb. but how snapchat works on MAgisk v7? can someone teach me?
[Magisk] mrceli:
Patiently waiting for magiskhide. ;)
[Magisk] InverseTV:
Uninstall Magisk, log in to Snapchat, reinstall Magisk.
[Magisk] Ninoh-FOX:
I install suhide 0.55 on magisk v7 (I don't unroot the phone) and safenet works fine in my phone (I erase factories apks and mod host file for adblock too)

Enviado desde mi E5603 mediante Tapatalk

---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------

Xposed 86.2 work fine with suhide 0.55

Enviado desde mi E5603 mediante Tapatalk
[Magisk] pndwal:
Little confusing what you now have; what does Magisk app report under Magisk, Installed, and under App, Installed respectively?

App should be at least as late as Magisk version. If not, update App. PW
[Magisk] pndwal:
No log files attached!

You could try extracting original boot.img from ROM package, then flash this from TWRP or PC w/ fastboot commands. Should boot again.

Then flash new Magisk; If zip (TWRP) install still gives issues, try recommend patch image / fastboot flash method. PW
[Magisk] dr4go:
@Didgeridoohan Could you please bring that to @topjohnwu 's attention? I'm pretty sure it will be overseen otherwise... Thank you!

Magisk v22+ produces a boot.img of zero size · Issue #4138 · topjohnwu/Magisk

Device: Samsung Galaxy S10 (SM-G973F) Android version: 11 (R) Magisk version name: 66e30a7 Magisk version code: 22006 As you know the Galaxy S10 is a SAR device without included ramdisk and boots f...

github.com
[Magisk] curiousrom:
Lol.

Apparently you are not an obsessive-compulsive backuper. ;)

***
[Magisk] pndwal:
... or alternatively, Recovery partition. 😉

👍

... and this is correct even w/ Magisk in Recovery, ironically; Magisk is always installed in the ramdisk of a boot image, even if it's a recovery boot image. 😆 PW
[Magisk] curiousrom:
You forgot to include a link to the page where you got that text from: https://github.com/topjohnwu/Magisk/releases ;)

Same here:

***
[Magisk] pndwal:
I assume you were patching recovery.img w/ Recovery mode check toggled on!

Perhaps John couldn't reproduce issue since you didn't specify 0 byte result only occurs if Magisk App is not unhidden / restored, and issue title was simply "Magisk v22+ produces a boot.img of zero size".

Why not create a new issue with clear title: "Magisk v22xxx produces a Recovery image of zero size on Galaxy S10 if App remains hidden" etc, as long as issue still exists using latest 22102. 👍 PW
[Magisk] pndwal:
Didn't forget!

Please see answer I gave you re. links to OP's up-to-the-minute updates / comments of less than 3 months ago. Guess you missed it:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84312597 😉

FYI, debug (Canary) repository has recently changed from https://github.com/topjohnwu/magisk_files/tree/canary to https://github.com/topjohnwu/magisk-files/tree/canary

Release notes are therefore now found at https://github.com/topjohnwu/magisk-files/blob/canary/notes.md

Nb. This link will not remain correct for cited Release Notes since it will always show the latest. Searches by commit / date give static address for specific builds. PW
[Magisk] RandomPooka:
It's systemless because it doesn't modify the system partition by default. Android checks the partition integrity at boot on most new devices.

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.
[Magisk] pndwal:
Yes, of course!

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.

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!

Actually, boot partition doesn't always contain ramdisk, and boot type ramdisk added manually by Magisk will also fail when bootloader support is missing, as is the case with the type III devices discussed here:

https://topjohnwu.github.io/Magisk/boot.html

Fortunately, there is a second Android boot image that can be used as an alternative; Recovery.img. As John Wu states:

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:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Magisk 'Recovery mode' patching option exists specifically for the purpose of patching recovery.img with Magisk properly, as boot partition ramdisk and recovery partition ramdisk configurations differ significantly.

Wiith 'Magisk in Recovery', boot.img can be left stock & unaltered. Generally however, 'Magisk in Boot' is the preferred option, especially as no special key combinations are needed to boot with Magisk root.

... As has been observed however, both of these 'Systemless' root options have advantages over solutions that alter system. Eg:

1) Ease of recovering from systemless mod failure causing boot issues. There are several methods to prevent these 'system overlays' from being applied, hence allowing system to boot normally.

2) Only Boot and/or Recovery partitions need restoring to take OTA updates (because actual system partition is unaltered). Also, as modules / Magisk settings are stored in /data partition, after flashing Magisk patched images again the mods / settings are restored. PW
[Magisk] dr4go:
1) Obviously.

2) As specified / already mentioned I would have mentioned it if I had known it before. I thought it was a general problem.

3) Sure, that would be plan B.
[Magisk] pndwal:
But you said you feel John will likely overlook your comments.

My feeling is that he won't if a new issue that states the configuration that results in the bug/issue clearly is opened. 🙂

I've seen other users reopen the same issue multiple times, but get taken seriously in the end... And yours does seem serious, especially as it may well affect other devices.

Didge. may well help however! 😉 PW