yashsingh1/xdaforums huggingface dataset:
[Magisk] Jiute:
Your right, i had some Magisk modules active before the OTA update. I guess i have to try and disable them... its gona be a mess because i don't want to Use TWRP... and last time i tried adb commands not rooted it didn't workout fine. I'll try to boot in safe mode...
[Magisk] zgfg:
Flash your patched img (by fastboot flash ...).

Then boot to Andriid Safe mode, and then immediately reboot to normal mode.

All modules and Magisk hide will be disabled - use Magisk app then to re-enable Magisk hide and to manage modules
[Magisk] Jiute:
Thanks for your help. I booted from the patched file through fastboot and entered Safe mode, then i shuted the phone down ans booted again through fastboot bu now the normal way... It Booted alright and i was able to patch de phone boot through the Magisk App on the phone. And now its rooted again.
[Magisk] MegaSharkXDA:
The specific use case I wanted to run on this device requires Google Play Services and this device doesn't have enough space for flashing Android 5+ plus Google Play Services, locking me on Kit Kat
[Magisk] pndwal:
Well, apparently it does!

How do you imagine so many others have updated from G thru R? 😁

You have 16 or 32GB internal, but need to repartition!

Did you check LOS 18.1 OP?

Instructions include:

5. In ODIN:

Auto Reboot : unchecked

Re-Partition: checked

PIT : i9100-LOS-16.0-Emulated-Storage.pit

PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

6. Press Start.

Methods to repartition GPT & PIT on your device have been around for some time. Old method here:

https://xdaforums.com/t/guide-enlarge-datafs-partition-and-get-rid-of-internal-sd-ums.2353551/

Another popular one:

https://xdaforums.com/t/mod-guide-p...-for-better-app-management-pit-files.2538947/

This is now done during installation process on later ROMs, incl. LOS18.1 in any case, as reported by XDA also:

https://www.xda-developers.com/samsung-galaxy-s-ii-unofficial-android-11-lineageos-18-1/

But maybe you don't want to check out / risk these mods. 😉

FWIW, I had a Huawei Ascend Y550 for years, which sported 4GB of device memory & 1GB RAM).

Initially, I had frequent low memory issues, but custom ROMs made it a new device (especially w/ Link2SD & Apps2SD app, then native adopted SD storage from Android 6 MM), and I was able to run LineageOS and GApps with no issues even without altering partitions. I updated from KitKat thru Nougat.

I believe I did have 1.2GB allocated for /system (and 1.7GB for user apps / data).

Your device may allocate less than 1.2GB for /system, causing problems loading GApps, but with preconfigured partitioning options available and 16GB (min) of device memory, running a custom ROM and GApps should be a cinch! (It's a no-brainer to me.) PW
[Magisk] 73sydney:
As @pndwal posted, repartitioning is the way to go (slight risks involved), but i finally only stopped using my S II when i couldnt get any more reliable batteries for it...up till that time id flashed every known ROM on the thing and repartitioning was the key

If only there was a safe way to do similar on the Pixel 2XL, its now harder to flash big GApps because some many devs are bloating ROM's with features and themes that i dont (and i assume most) dont really want...i do miss the PIT days...

fwiw, i never had an issue using PIT files. Usual caveat/disclaimer applies, make sure you have a backup of anything you love on any internal or external storage before you begin
[Magisk] Jwtiyar:
Hey i flashed magisk on custom ROM running miui(android R) Xiaomi mi9 has NO ramdisk, After every update with the ROM i have to patch boot image, is there any way to avoid patching every time? Just patching twrp recovery once and installing after every update?

Patching custom revovery does not work device will not boot, just patching stock boot.img will work.
[Magisk] Compgeek316:
Manually Install Magisk Manager Apk as System

I had the same issue. Extracting "Magisk.apk" from "phh-superuser-magisk-v2.zip" and installing it as a system app by coping the apk to /system/app and then restarting worked for me!
[Magisk] nomadism:
Ditto. I had to do this also.
[Magisk] HypoTurtle:
That kinda defeats the purpose; this is a systemless framework and as such /system should always be treated as read-only.
[Magisk] Captain_Throwback:
Agreed; however using the Magisk installer template, the APK can be installed to system systemlessly ;).
[Magisk] rgawenda:
I've managed to fix this issue by dirty flashing Magisk v1, uninstall Manager from Settings-Apps, installing the extracted Manager from phh's superuser v2, and flashing again both Magisk v2, and phh's superuser v2
[Magisk] CSX321:
It might be, as the OP mentioned earlier, a signature issue. I just now uninstalled the v1 Magisk Manager, then rebooted to TWRP and installed Magisk v2 and the compatible phh Superuser v2, rebooted normally, and everything is normal. v2 of everything is installed and functioning, including the Manager. This is an N5 with ElementalX kernel, no Xposed.
[Magisk] lightningdude:
Nexus 5x, uninstalled Magisk Manager, then went into TWRP and flashed Magisk v2, then phh's superuser v2 and the updated xposed. Upon reboot, I had the updated manager without extra work.
[Magisk] Chahk:
No need for reflashing, this will work just fine:

adb uninstall com.topjohnwu.magisk
adb install c:\Magisk.apk
[Magisk] HypoTurtle:
Of course but that wouldn't be done by manually copying and placing it in /system [unless I'm mistaken]. I'm still trying to wrap my head around how the dummy files are added; only think I can think of is that it's akin to xbin_bind from systemless-superSU [folder bind-mounting] but that would require an excessively large .img - and file loop-mounting like I'm doing with syst-SU on RemixOS at the moment obviously is too simplistic and can't introduce new files for line in $(find /su/vendor/ -type f); do mount -o bind $line /system/$(echo $line | tail -c +12); done; - not a bad one-liner though.

What should work is placing it manually at /data/Magisk.apk and rebooting = that should place it in correct folder for a userapp. If the zip isn't adding/installing it properly.
[Magisk] dancer_69:
I installed v2 and I have the same problems with Magisk Manager. Root mount status doesn't change and selinux radiobutton re-enables itself.

Unroot seems to work though. I can see it in magisk.log and also I cannot login to root account from terminal emulator by "su" for the time I set in Magisk Manager. Root works after that time and I "su" gets me to root when the time pass.
[Magisk] bmg1001:
Installed V2 (and phh's root) on Nexus 6P with N DP5 and File-Based Encryption enabled. Everything works fine! I was able to add a card to Android Pay, but I haven't made a purchase yet. Usually, adding a card means it will work when making a purchase. Great work!
[Magisk] :
The real test us making a purchase, adding a card does not mean purchases will work.
[Magisk] Artim_96:
very strange: after the latest update, Magisk seems to be working even worse than the first version (logs, that I was able to get: http://xdaforums.com/showpost.php?p=68045430&postcount=1494, boot logs where not working since the adb command only created an empty file, adb was enabled in dev settings). There at least I had the Magisk App and at least was able to grant SU permissions even if no app could use it.

Now, I see the Magisk.apk and Magisk.img under /data, but under /cache I only find a folder "magsik" with 5 subfolders, which are all empty (in TWRPs filemanager) but no magisk.log. I also have no Magisk app in App drawer (flashed only Magisk v2 and phh-superuser-magisk-v2 and installed the phh SuperUser app) and the SuperUser App only says the su binary is outdated, so root seems to be not working at all.

What I did: uninstalled SuperSU from it's app, reflashed the whole system over ODIN and installed TWRP (3.0.2-0), deleted /data/su.img and /supersu and flashed the magisk and phh's SuperUser zips (log attached)

Device: Note 4 SM-N910F, official MM with Patch level from June 1. The only mods I'm using (which are all not working since root isn't available and I didn't even tried to flash XPosed) are Titanium, Greenify and XPosed Installer with some Modules. Bootlog.
[Magisk] topjohnwu:
OK guys, I got Samsung non-boot issue fixed.

I'll also switch to the highest compression for ramdisk to fix devices that have no free space for boot image.

Also fixed the unroot issue with non-rooted custom roms.

Final work is to deal with some potential sepolicy issues, the next update should be tasty :)
[Magisk] narwahlberg:
Is there any way to get the old toggle method for root instead of the timer?
[Magisk] Skyrocket2Paradise:
I'd love to know as well. At least for me the toggle makes a lot more sense or at least the option for a toggle or timer. Thanks again for your work [MENTION=4470081]topjohnwu[/MENTION] !
[Magisk] rtthane:
I'd 3rd that, or at least a button to re-enable root to override the timer. Regardless, this is a superb piece of work!
[Magisk] KaMyKaSii:
I believe that with code changes in the new version the toggle would be a button to "turn off until the next restart," then timer is the most viable
[Magisk] elreydenj:
Has anyone successfully gotten v2 working with regular superSU or will that never be an option. Many are much more comfortable with chainfire's version.
[Magisk] KaMyKaSii:
It has a modified version of SuperSU this topic. It's functional, but if you want Android Pay working, forget it.
[Magisk] 4930:
Please explain a bit more, I am interested in doing the same
[Magisk] negroxxx:
I can play pogo

install SuperSU 2.78

magisk v7

suhide

microg

I'm happy safetynet step
[Magisk] bpear96:
What is MagiskHide? I only have magisk with no root installed. All I want is the action launcher systemless module.
[Magisk] Drefsab:
id be intestested in finding out what magiskhide is as well, basically my ideal world would be something that would let me have systemless root, busybox and viperfx audio and have the abililty to toggle hide these to watch sky go.
[Magisk] Ninoh-FOX:
New block for safetynet...

Enviado desde mi E5603 mediante Tapatalk
[Magisk] teddy0209:
Magiskhide is still under development... From the word itself, it's to hide magisk...
[Magisk] knipp21:
Yep...the last 3 pages all say that...
[Magisk] ElRongMcBong:
Someone have root problems too, after update to Magisk v7 & phh's r259 ?

Some Apps like ES Fileexplorer Pro or Hex Editor Free say can't get root, coz i haven't root O.o, but other Apps like Terminal Emulator or Titaium Backup works like all the time befor
[Magisk] Captain_Throwback:
The apps are the problem. They are looking for the su binary in a hardcoded location. Talk to your app developers.
[Magisk] ElRongMcBong:
what is the different Magisk v6 & v7 or old pph's and New ones?

With v6 and old pph's they work ?
[Magisk] soder:
When you say that Xposed been tripping SafetyNet for a while, do you mean the "normal" Xposed then, the version that's not Magisk module?

Because, I've been on SuperSU+suhide+Magisk+Xposed and passing SafetyNet (until today or something).

Thanks.

/Söder

/Söder
[Magisk] Captain_Throwback:
I mean systemless Xposed, in general. The only reason it was working for you is because of suhide. Xposed alone still would've tripped SafetyNet without it.
[Magisk] dl200010:
I have searched google and XDA but for some reason cannot find the answer to my issue. I have the Nexus 6P running the very latest version ROM and phh seSuperuser 259. Every time I try to install Magisk my phone won't boot. I am running stock (Oct 2016). When installing I flash the stock boot.img, flash Magisk v7, and than flash the Magisk version of phh seSuperuser 259. It boots up, only to the "Google" logo, and reboots. Than it is stuck at the "Google" logo. I reboot into recovery and I cannot find any logs from magisk. I am than forced to flash the stock boot.img and flash the official phh seSuperuser.

Is Magisk compatable with an encrypted Data partition and with Android Nougat?
[Magisk] Didgeridoohan:
I'm running Magisk an encrypted Nexus 6 and stock Nougat. No problems. Gonna put Magisk on my wife's Nexus 6P this weekend, also encrypted and stock Nougat. We'll see how it goes, but I do believe I've seen other 6P users reporting success.

Edit: Magisk v7 and phh's 259.
[Magisk] edyny1:
yup
[Magisk] dl200010:
Did you use the magisk modded seSuperuser or the official one? Mine just sits there and does nothing until I flash back.

Edit: Not the new Nougat file level encryption. Still using the full disk that Marshmallow and before used.
[Magisk] Ch3mist:
for some reason when i flash magisk uninstaller in recover it isnt removing v6
[Magisk] CrazyCypher:
Hy guys, did anyone try to swap the Google play services with microg?

What are positive and negative things worth mentioning?

What would I loose if I swap it?

Thank you for answers, I appreciate it
[Magisk] Artim_96:
Well, it only has since basic stuff built in since it can't user anything from Google. So it should be impossible to use any app that relies in SafetyNet because I highly doubt that anyone is able to rebuild it in a way that it brings the answer the apps need... Otherwise there would be XPosed modules to manipulate that and nobody would really give a thought about suhide and stuff
[Magisk] mobileman88:
This is getting to be such a pain. r266 no longer works. Would need to have a way to unroot and easily reroot without the PC.
[Magisk] pndwal:
Yes, being Xiaomi, although you have no FACTORY ramdisk in boot.img, you DO have bootloader compatibility with boot ramdisk, so, because Magisk actually ADDS basic ramdisk (not needed for boot in the case of type III devices, but needed to initialise Magisk), patching boot.img still works.

On most Xiaomi devices, experience has been that patching Recovery image generally doesn't work despite Ramdisk = no, as it seems you know.

I understand that to take OTA on non A/B devices (if that's what you mean), there is no way to keep root. (It is possible on some A/B devices).

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

All non read/write images (boot, system, recovery, vendor etc) MUST be stock / unmodified (or restored) to take incremental OTA updates safely. Nb. This doesn't apply to full image updates labelled OTA.

For this reason, updated boot.img will need to be patched each time.

You can, however, try this if you don't wish to download full ROM to extract boot.img:

Restore all images, Take OTA, Flash TWRP, Do nandroid backup including boot.img, Rename boot image backup (boot.emmc.win) to boot.img, Patch this from Magisk App, Flash that. 🤠 PW
[Magisk] Jwtiyar:
Than you for the answer

Now i did patched stock custom ROM boot.img with recovery mode checked and not checked, after flashing both still no magisk installed.
[Magisk] zgfg:
OTA installation overwrites Boot, hence you have to patch the new boot.img with Magisk and flash it

Since you're patching boot.img (not recovery.img), Recoveey option must not be checked - and the patched img must be flashed to Boot partition

If Magisk app does not detect Magisk - make sure that you did unhide Magisk app if you previously took Hide Magisk app/mngr - if needed, find Magisk app/mngr in Settings, Apps and remove all such apps (incl. the renamed version if you did Hide Magisk nngr/app), and then install again the Magisk app

I'm also on Xiaomi. I do not accept automatic OTA but download myself the zip file from e.g. Xiaomifirmwareupdater.com

Then I extract boot.img and while still not yet upgraded MIUI, I patch that img in Magisk app.

I make sure that Magisk app/mngr is not hidden and (to avoid possible bootloops) that all Magisk modules are disabled.

I enter TWRP, flash the downloaded MIUI upgrade zip, wipe Dalwik and Cache and then also, from TWRP, flash the patched boot img (as I prepared earlier - see above).

From TWRP, Advanced, File mngr, I also delete the folder: /data/system/package_cache

Finally I boot to system, Magisk is back on and I have upgraded MIUI.

Open Magisk app and manage/enable (one by one with rebooting) the modules

Similar procedure when updating Magisk - no flashing the MIUI upgrade zip, but (after unhiding Magisk mngr/app) install the new Magisk app. Then patch the boot.img (or take the risk and do Direct update) and flash the patched img

I'm using Magisk Canary (more often Magisk updates than for Stable) and (for many months now) Xiaomi.eu weekly (A11 - upgrades come almost every week).

By following the above procedures I never had bootloops, Magisk not detected or other (oftenly reported issues here when users do change/upgrade systems or Magisk). Some work to do each time but much less than fighting the possible troubles

In fact, I never hide Magisk app and I take the risk that I do not disable Magisk modules (knowing very well how to resolve if the bootloop would happen)
[Magisk] pndwal:
Uninstalled any older Magisk Manager app (hidden/renamed or unhidden) before installing new Magisk App (especially if coming from pre Magisk v22)?

Patched boot.img from latest ROM update with Recovery mode UNCHECKED, then flashed from PC using ADB Fastboot? PW
[Magisk] Jwtiyar:
Thank you guys, The problem was the hidden magisk it was not uninstalled(I am foolish) and when I uninstalled it worked very well.

Thank you again guys.
[Magisk] pndwal:
Just out of curiosity, were you updating Magisk from pre. V 22? Or was it V22 or v23 that was hidden? PW
[Magisk] Jwtiyar:
Iam using canary build v23001
[Magisk] pndwal:
Interesting! So it was also this version Magisk App that was hidden from before OTA? Not a pre v22 Magisk Manager? PW
[Magisk] Jwtiyar:
Yes i hide canary version, because normal version not passing safety net with me.
[Magisk] pndwal:
Ok... But SafetyNet Test should also be fixed since public Stable/Beta 23.0 (22103 debug Canary):

"Bug Fixes

[App] Update snet extension. This fixes SafetyNet API errors."

https://topjohnwu.github.io/Magisk/releases/23000.html

... But if you didn't also update Magisk from pre 21406, this confirms that failing to UnHide Magisk App before patching is still causing patching failure on some devices.

That was an expected / documented issue moving up from pre. 21406 due to incompatible changes:

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

but it shouldn't be causing issues when only compatible newer App is installed, although this was reported earlier.

It's interesting that the issue persists in 23001. PW
[Magisk] daddylonglegs:
Thanks so much for the reply.

When I do an update to my OS, what I do is I download the FULL firmware from Google, not the OTA but the full download. Then I open flash-all.bat and I delete the -w command. I then run flash-all.bat.

Is that the right way to do it?

I just disabled Systemless Hosts and rebooted and my Pixel 3A still has really bad lag. Is disabling it enough or do I actually have to delete it?

When Magisk is uninstalled my phone has no lag.

The only reason I'm even using ElementalX is because back in January when I did an update to my phone and re-installed Magisk, I couldn't even get my phone to boot with systemless hosts enabled. When I installed ElementalX, it worked with systemless hosts.
[Magisk] YLNdroid:
Hello Magisk users.

Device - Model / Code: Samsung Galaxy J5 2016 (SM-J510FN) / j5xnlte

Build Number: NMF26X.J510FNXXU2BRJ4

Android Running Version: 7.1.1

Communication via ADB is established and functional. However, after executing

adb reboot bootloader

and my device having booted into Download Mode,

fastboot devices

just jump to the next line for inputting command/s.

fastboot reboot

outputs / displays <waiting for any device>

OEM unlock has previously been enabled; Samsung USB Driver for Mobile Phones version 1.7.23.0 is currently installed on PC.

I presume the bootloader is unlocked, since I was able to flash TWRP using Odin3 (v3.10.7).

I downloaded the

TAR

file

of the BRJ4 boot image from firmware.mobi and patched it via the Magisk app.

Do I simply proceed to flash the

patched boot image TAR file

via Odin3's AP section?

Please apprise me if I have overlooked anything, or if I need to employ a different procedure.

Thank you for your patience with my naivety.
[Magisk] J.Michael:
@daddylonglegs Have you tried removing all of the apps from the "hide Magisk from these apps" list?
[Magisk] mistermojorizin:
I'm testing Android 12 beta 1 on my pixel 4a5g. A lot of apps crash if added to magisk hide. If removed, the spa complain about root. Is there anything I could try? I'm using the canary version of magisk.
[Magisk] J.Michael:
Have you read @Didgeridoohan's reference manual?
[Magisk] mistermojorizin:
Yes, but I didn't s see it taking about magisk hide crashing apps
[Magisk] pndwal:
This:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85049767

It is in @Didgeridoohan's wiki too:

https://www.didgeridoohan.com/magisk/MagiskHide#

https://www.didgeridoohan.com/magisk/MagiskIssues#

Nb. A statement that follows the above, "Note: It's not about the number of apps on the list, but which apps are added" is probably incorrect. The number of apps is also critical as seen by John's explanation (ref from post linked above) re passive reaction limitation of MagiskHide daemon:

PW
[Magisk] dpiehl1:
I've been using Magisk on my Pixel 3 XL since earlier this year and decided to update to Android 12 beta1 this week. Using the Canary version f822ca5B (23001) (21) / Canary Channel, I created my magisk_patched image and using fastboot flashed it. After reboot, my lock screen and asks for PIN as usual, when I enter the PIN, it looks like it going to let me in but then it jumps back to the lock screen. I've read through and saw that disabling verity has been suggested but that made no difference.

Any thoughts on what I'm missing?
[Magisk] HippoMan:
Has anyone heard of something called "MagiskLite"? I was told that it's a utility which automatically installs Magisk only when it is needed, and then somehow uninstalls it until it is needed again. However, I haven't been able to find any info about this app, and so I wonder if it even actually exists.

Any thoughts?
[Magisk] pndwal:
Yeah - I was going to ask if it's a bit like a Clayton's beer; "The beer you have when you're not having a beer"! 😁

Anyway, I just did a quick search, n see Nangong Xueshan ( www.twitter.com/vvb2060?lang=en ) prolific Magisk colaborator @vvb2060 (next John Wu?) hosts a Canary build with smaller file size, and json file for custom channel Installation is lite.json.

Eg, his latest v23001 app-release.apk is 9.84MB. John's v23001 app-debug.apk is 12.7MB.

https://github.com/vvb2060/magisk_files/tree/99709fff6a2bb7cb793aeb170d5d36d463451492

I have no idea if this is what you heard about, but I'm guessing it's the most likely candidate... And, more importantly, should be a trustworthy one, as John has sung @vvb2060's praises before.

Interesting also, he has separate '32' and '64 bit' builds in his Alpha branch. PW
[Magisk] tinbilly:
Magisk: canary build version f822ca5b

Device: moto G8 Power XT2041-1

ROM: crDroid 7.4

"Permissions: No permissions requested" is greyed out. Thus I cannot install module using "Install from storage".

Much appreciated any advise.
[Magisk] zgfg:
Installing from storage only needs to open File Mngr and to locate the zip. You should not need any special permissions (module installs to /data/adb by use of root grant)

With missing storage permissions you would fail to install a module from Repo - in that case, Magisk app downloads the module to Downloads folder and automatically installs from there (as if you would Install from storage, navigating to Downloads folder)

Hence, try installing from Repo

Precisely describe what happens when you try to install from storage.

I remember that somebody had a problem with File Mngr that Magisk was calling. It didn't properly recognize zip files and thus Magisk was unable to install a module from storage

Magisk app does not have a built-in File Mngr - it will call the default one on the phone (usually Files)