yashsingh1/xdaforums huggingface dataset:
[Magisk] ktmom:
Admittedly I'm not a Samsung user, but it sounds like your trying to install Magisk to the boot.img. I am pretty sure for your SAR A-only device, which was originally released with Pie, Magisk gets installed to recovery. The recovery mode box gets checked when you are patching the recovery image. If you haven't yet, see the instructions here. Make sure to read the link on that page "Magisk in recovery".
[Magisk] Sephious13:
My apologies. I was just being very stupid. There was nothing wrong with the installation. I was just not using the correct OEM combination. Thank you.
[Magisk] AndresOrue:
Hi anyone know where magisk saved my current version , I need to reinstall it but in the official link I only have the lastest version? I am using the Canary version 20.1.5c
[Magisk] pep01:
The Magisk I use is stable and I am not connected to any firewall. This happens on the device when I connect to the network via Wi-Fi or 4G. And I don't have any restrictions for Magisk. I use the same configuration as before but when updating Magisk to the latest version this happens. I have updated Magisk with the Ambassadii 2.2 rom and I have also tried the Ambasadii v8 doing full wipe. I have also downloaded the zip file here from the official Magisk thread here in Xda to install it again but the same thing always happens.

Enviado desde mi SM-G965F mediante Tapatalk
[Magisk] ALdelSol:
I have the same problem, for a few days in a redmi note 7 and in a mi 9T with MIUI 11 and with MIUI 10, he stays all the time looking for updates and from there it does not happen
[Magisk] ktmom:
If you flashed in recovery, then the un-patched image should be in /data. It will be a .gz file.

If you manually patched then Fastboot flashed the patched boot.img, Magisk doesn't (can't) backup the stock boot.img.
[Magisk] jcmm11:
Actually it does backup the boot image, it just sticks the backup in a different place. It places it in

/data/user_de/0/<package name>/install/

Where <package name> is the, obfuscated if hidden, name that Magisk Manager is installed under. This, obviously, is on the device used to patch the file - which may or may not be the one where it's installed.
[Magisk] ktmom:
Is that a canary thing or start recently? I don't have an install/ under /data/user_de/0/com.topjohnwu.magisk/. Doing a complete search on my device, there is no *.img.gz found. Though I am still running 19.3 on a Pixel 3XL.
[Magisk] jcmm11:
It's always created a backup (as far as I remember), but I think the locations moved around some.

Grab a stock image. Patch it. Then look in both /data/user_de/0/com.topjohnwu.magisk/ and /data/data/com.topjohnwu.magisk/. It will be in one or the other. Obviously check all the subdirectories.

That backup can get erased so if you haven't patched recently you may not find it.
[Magisk] mspasov:
For me the path is:

/sbin/.magisk/mirror/data>stockbootimage...

Nothing found in user-de or data/data
[Magisk] ktmom:
Yup, definitely there (/data/user_de/0/com.topjohnwu.magisk/install), but wasn't there prior to patching again. Possibly it was lost as a result of a manager update.

[MENTION=4667597]Didgeridoohan[/MENTION] would adding this information to the online documentation be ok? Though my take has always been if you're manually patching a stock image, you should save it :)
[Magisk] skoon5:
The bank APK showings error..

In android : 9

Note 10 plus

Room LightRom

Bank Muscat
[Magisk] lovemyram4x4:
I have a strange issue, well more of any annoyance. It started after in stalling the Nov Android 10 update and I'm running the current stable of Magisk. After I boot the devices Magisk manager keeps opening several times, which seems to be each time it grants superusers to apps as they start back up after boot. After awhile I only get the normal toast (turning off toast doesn't stop manager from opening). What's even odder is if I set screen lock to none this doesn't seem to happen (I notice this because on my Essential phone I'm seeing this on I have to turn it off or TWRP fails to decrypt, so the first boot after doing something in TWRP I don't the issue with Magisk manager). Another odd thing I noticed was after I first flashed the Nov patch, i had 2 Magisk managers in the app drawer until I opened one then there was just 1.

I'm not looking to get this fixed as it's not really a problem. I'm just wondering if anyone else has this this?
[Magisk] Hyflex:
Hi,

I just updated my Pixel 2 XL to the latest available Stock ROM, updated Sultans Kernel & Re-flashed Magisk... however reboot I regularly get "Phone is starting..." and also "Magisk Manager keeps stopping".

I can't get into Magisk Manager to enable debugging to get a copy of the logs... what can I do?
[Magisk] Badger50:
Flash the stock boot.img to both slots, boot up, then put a copy of the stock boot.img on your device. Patch that .img with magisk, move the patched .img to your pc, then fastboot it to both slots with...

fastboot flash boot magisk_patched.img --slot=all

Then boot up, you'll have root, then flash sultan's kernel with EXKM or FKM, don't reboot yet, then flash the magisk.zip in EXKM or FKM, then reboot, and you should be good :good:
[Magisk] :
I have never flashed things on both slots :silly:
[Magisk] Badger50:
Each to their own bruh :cool:
[Magisk] Homeboy76:
I don't think that is true. If you flashed the stock Factory Image, the 'flash-all.bat file flashed some files to both slots. One of which is the boot.img
[Magisk] Idiyeet:
The update went safely with no problems. Thanks for your quick response regarding it. Much appreciated!
[Magisk] :
That's the script, not me :silly:
[Magisk] Homeboy76:
Ok, but you implemented the script. :eek:
[Magisk] demonoidmaster:
Flash-all is found in all fastboot flashable roms
[Magisk] Homeboy76:
That maybe true but you have to implement it. It doesn't implement by it self.
[Magisk] gpablo1:
Maybe the update search loop problem that many of us have is because the update server has been blocked by the authorities. See attached image.
[Magisk] jcmm11:
That's the path if you patch stock via TWRP. It's the same as /data/<stockbootimage>

All of /data is mirrored there.
[Magisk] lividhen99:
Try a vpn
[Magisk] gpablo1:
Thanks! I tried with a VPN and it works. Magisk manager works well. The update search loop problem is for some restriction in my country (Spain, maybe in europe too) for accessing the server.
[Magisk] Philnicolls89:
Hi everyone, I hope this is the right thread for this question. I am on magisk 20.2 and manager 7.4.0, all my previously installed apps have root access however any new apps i try and install aren't requesting superuser access. They aren't even coming up in the logs as denied, it's as if I don't have root when I try to install a new app. Has anyone come across this issue? I'm not sure how recent this issue is as I don't often install new apps!!
[Magisk] lividhen99:
Yay! Glad it worked! So, I guess to anyone that is having the same issue, use a vpn.
[Magisk] JudgeDread11:
Does that mean they block GitHub?

Aren't a lot of professional developers relying on GitHub? If so it would hurt their own local economy.

Sorry for OT.
[Magisk] lividhen99:
?That would be problematic wouldn't it. Are they able to just block a repo? Is that a normal thing?
[Magisk] ashyx:
Why don't you just change your DNS servers to something like OpenDNS?
[Magisk] gpablo1:
The Spanish government is investigating websites related to Catalan independence and with possible involvement in political terrorism, and as they suspect that Github's server is related to some of these issues, since he has closed access to the server to all Spaniards.

Specifically to this website: https://raw.githubusercontent.com/
[Magisk] ALdelSol:
and as in Spain, our "rulers" fix everything very quickly ...... we don't access those pages again in a long time

---------- Post added at 01:39 PM ---------- Previous post was at 01:28 PM ----------

In Europe not because I just connected to a VPN from France and it already works magisk and all the pages that I could not connect from Spain

---------- Post added at 01:55 PM ---------- Previous post was at 01:39 PM ----------

To not lose network speed instead of connecting to VPN I changed the DNS with an app from the Play Store and it works without losing network speed
[Magisk] star.seraph:
Hello everybody.. Magisk 20.1 and latest Manager deny root access to every app in MIUI 11 what should I do?
[Magisk] palmbeach05:
Abandon miui and get a better os. Miui has had numerous problems lately with magisk, but magisk works everywhere else
[Magisk] jbradshw:
Moto G5+ / Android 9

So I'm currently on Magisk 19.3 and it wants to upgrade to 20.1 (I updated the manager app to 7.4.0). I've read the documentation that Magisk will now reside in recovery instead of the boot area, and it says I'll now need to patch the recovery image (TWRP) and flash that going forward. So my question is, if I click on Update in Magisk Manager (to update from 19.3 to 20.1), is it going to do that for me on this update (and future updates?), or am I going to have to manually patch it myself and flash it? I've mainly hesitated on updating because of this ambiguity.
[Magisk] ALdelSol:
Well, I've never had problems with MIUI. Now I have a Mi 9T and a Redmi Note 7 with MIUI 11 and magisk if it grants me root permissions. Look to see if you have given the necessary permissions to the magisk app
[Magisk] ktmom:
In addition to [MENTION=7415094]ALdelSol[/MENTION] comments above, did you do an update from a previous version of Magisk? Was the manager hidden/repackaged prior to the update? If so, did you restore it before doing the update?

Have you tried uninstalling the manager, rebooting then reinstalling the manager?

---------- Post added at 12:53 ---------- Previous post was at 12:32 ----------

The instructions at the top of the Installation page should just work, since you're upgrading.

I'm not sure where your reading that your device needs root injected into the recovery image but I guess that suggests it's a non A/B device, using SAR (system as root) . To make sure you understand what is needed for your device, take a look at;

Knowing Your Device.

Additionally, you have a custom recovery:
[Magisk] jbradshw:
I can't recall where I read it but when Magisk 20.0 came out, there was a notice to read this page on the changes that were made, and I could have swore I saw it said that Magisk was moving from the boot partition to the recovery partition. Maybe I read that wrong.

Also "getprop ro.build.system_root_image" returns nothing. When I type just "getprop" it doesn't appear in the list. My device is not A/B. I'll just proceed with the update. Based on the install page it appears I'll be fine.
[Magisk] ktmom:
I suspect that the discussion about the need for SAR A-only devices needing to use recovery for root over time generalized to root moving to recovery. It's a "limited" number of devices that are affected (at this time).

"getprop ro.build.system_root_image" also does not exist on my trusty Nexus 6. Which means you're not affected by the changes from Google.
[Magisk] Skyjersey:
Try downgrading to Magisk 19.2 it works on my Samsung S5 with custom Pie rom.
[Magisk] PoochyX:
Damn that galaxy 5 still having support for new custom roms all these years

Later

([emoji3590]09-09-18[emoji3590])
[Magisk] guest4711:
[OT]As long as there is an active community....

My Galaxy Nexus is still getting updates, too...

[/OT]
[Magisk] ltf_195:
Unable to OTA update - A/B partion

Hi, I'm unable to apply OTA update

What I've done:

Go to magisk manager > uninstall > restore image

Got notification "restore done"

Download OTA update

Apply update> error "Couldn't update, installation problem"

I notice that after restore image, my apps still granted SU right and root detection app still don't detect root on my phone. Is this normal?

I also check that my System partition haven't be tempered.

Magisk version 20.1

Magisk Manager 7.4.0
[Magisk] Johnn78:
Me too. This trick works once for me. All the rest times, I couldn't apply the update & the only method in which I do, is to find the update in twrp version & when I flash it then I flash twrp & magisk in both slots.
[Magisk] Ch3vr0n:
In that case I'd flash the factory image of your current build (but remove the -w flag so your data doesn't wiped). Root it again, then immediately after retry the procedure (restore, download reboot)

I had that a few times too. I did the above and since then I've been able to apply at least the last 4 ota's successfully using the image restore procedure
[Magisk] Johnn78:
Factory image you mean this which you can make backup from twrp in backup options (the system image which has stable size 3072 Mb & NOT the system file whise size is variable).
[Magisk] :
OT: what rom do you have on your GNex?
[Magisk] jcmm11:
He means the image you download from https://developers.google.com/android/images

(Assuming a Pixel device). The -w that has to be removed is found in the flash-all bat/sh file.
[Magisk] Antidote03:
Hello fellas

First time post a an issue here .. and i apologize if this the wrong section

My device xiaomi K20Pro 8gb/256 with miui 11(Android 10)

Stock eea rom

My device non A/B Partitions

Tried to root it via twrp like any device its always reboot back to twrp... I tried other method by patching boot.img via magisk manager and flash via fastboot command or twrp still same thing (reboot back to twrp)

I noticed the stock boot.img size 120mb while the patched boot img reduced to 32 mb

I hope you find any fix for this

Thanks in advance

Sorry for my bad English
[Magisk] ashyx:
Size of pulled boot image is irrelevant, most of it is free space which gets removed when repacked.
[Magisk] user822:
I have a rather odd problem:

My Oneplus 7 pro simply does not boot when Magisk is installed

Installed Magisk 20.0 on Stock 10.0.1-GM21BA with unoffical TWRP a while ago and everything was fine.

Today it won't boot any more (stuck on the warning that my bootloader is unlocked, then bounces directly to fastboot, without showing the normal boot logo)

As soon as I uninstall Magisk from TWRP it boots again

Then I Install Magisk 20.1 from TWRP, it does not.

Then I uninstall Magisk 20.1 from TWRP, it boots again

Then I flash the pre-patched boot image from here and it does not boot again

Then I flash the stock boot image from here and it boots again

I also tried installing Magisk without dm-verity (only forceencrypt), still not booting beyond unlock warning and fastboot

Does someone know what is going on with my phone?

Somehow it must be unhappy with the Magisk patched boot image suddenly, but the TWRP patched boot image is no problem

Thank you for any help
[Magisk] JudgeDread11:
Sounds like a module is causing problems. Maybe edxposed.

Issues like that have been discussed many times.

Fastboot TWRP and then delete the modules.
[Magisk] user822:
Unfortunately that does not seem to be it

It is not bootlooping, it is never even getting to a point where the boot animation starts, as if the kernel were invalid

Magisk was also running in core-only mode previously (the .disable_magisk file is still present), with zero modules installed
[Magisk] ktmom:
Your device was released with Pie (2019) and you say it's not an A/B device. I think you'll find you need to install root to recovery, not boot.

See Magisk installation instructions, especially the "Know your device" section.
[Magisk] Johnn78:
Did you try with older version of Magisk for example v19.4 ? In my Mi A1, with v20 I wasn't able to boot in recovery partition becasue it appeared destoyed system while with 20.1 was ok but something happens with mounting of system becasue I can't use third party software to uistall system apps. For this reason I have stayed with v19.4 & the both problems has been resolved. Try the v19.4 & tell me if you could root it or not. Also to suppodse that you tried & the other method in which via magisk manager you create patched boot.img (it converts the stock boot.img with magisk embedded) & via adb to flash it.
[Magisk] user822:
Creating a patched images from Magisk Manager and installing that one boots, however it complains about Magisk not being installed :confused:

Something seems seriously weird

I always made sure I use the correct slow as well

Installing Magisk 20.0 again also did not work, weirdly enough it booted, but the Manager does not detect it either
[Magisk] Johnn78:
Let try via twrp to flash magisk 19.4.
[Magisk] macc_k:
Hide Magisk Manger failed

I'm having a problem while trying to hide the Magisk Manager?

I always get the "Hide Magisk Manger failed" message in every versions of Magisk I tried.

My device is Xiaomi Redmi Note 8 Pro 6/128 with MIUI 10 (Android 9.0)

Here're what I've tried:

• Magisk v. 19.4, 20.0, 20.1 & 20.2 on Global ROM V10.4.1.0 and V10.4.2.0

• Magsik v. 19.4, 20.0, 20.1 on EEA ROM V10.4.5.0

I can gain root access on all of the above scenarios without any problems, except I can't seem to hide the Magisk Manager package.

Can somebody please help?
[Magisk] Antidote03:
Dammit . Sorry for Miss spelling I was gonnaa say my device is system as root... But still not working via flashing patched img via twrp
[Magisk] zgfg:
You say your device is SAR, not A/B - did you read instructions

You should not patch through TWRP, and not boot img:

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

And be aware that on read-only System, you must enable systemless hosts for e.g. AdAway
[Magisk] Utini:
Hello everyone,

I have magisk 20.1 and Manager 7.4.0 installed on my Nexus 6P with Android 8.1.0.

I am hiding Magisk from google play store, google play services and my banking app (DKB Banking, DKB TAN2go).

I also have "Magisk Hide" enabled in the options

How ever, I cannot "Hide Magisk Manager" as it just gives me an error message "hiding failed".

I believe that is also the reason why I cannot start my banking app. Can anyone tell me how to this fix this and hide magisk manager? :/

Thanks!
[Magisk] Karitoriki:
That's a pretty piss-poor excuse seeing as how the Canary builds are supposed to have all the features of the current public along with experimental additions/changes, yet they're not obfuscated. Not to mention Magisk hide worked perfectly fine prior to the obfuscation - I strongly suspect it was added solely to prevent modification by users, which goes against the entire point of rooting your device.
[Magisk] Artim_96:
deleted
[Magisk] JudgeDread11:
Canary DEBUG builds, and I guys they are not obfuscated because it would interfere with the debug functions.

Canary builds are also Pontiacs I believe.

Please somebody correct me if I'm wrong.

In any case, a bit more respectful wording would be appreciated even if you do not agree with developer choices or answers to your questions.
[Magisk] dr4go:
Applause.

Sometimes I (still) wonder regarding today's society in general and as well what people even do here on xda, a development forum, asking the same questions over and over again without the will to search even once before posting ****. What's even worse: demanding stuff for free. Develop it yourself, period.
[Magisk] Didgeridoohan:
I can assure you that there is no such intent...

The fact that theming the Manager might not work with the way that it is hiding itself is known. But, as I wrote, function is in this case deemed more important than form.

There's a major remake of the Manager under way, separate to the rest of development (take a look here if you want to follow the work), and if my memory isn't failing me miserably [MENTION=9815783]diareuse[/MENTION] is planning on some cool theming features.
[Magisk] agentdr8:
In my experience, yes.
[Magisk] Chaos234:
Hey thogether,

I have a problem with magisk and pokémon go because it does not work on SM-T805 with the latest IronRom/Kernal installed which has magisk compleatly included.

Installation was a few minutes ago compleatly fresh. The only thing which samsung let me not toggle is the SELinux state (currently permissive) but the first option is

toggle able and it is toggled to green state.

All what I get is that I can't authenticate with the service (like the time where the server are down before rooted devices where banned from the game).

So what can I do now to can play with the latest version which I have gotten from the play store?
[Magisk] crackers8199:
can anyone help me with this? if i can't get the ability to make a backup working, i'll probably just go back to system root...even more so since android pay no longer works with systemless xposed, which was my whole reason for wanting to get magisk running to begin with. anyone?
[Magisk] QWEnter:
How to install Magisk v6 on Sony Xperia Z1 Compact (D5503) (Stock ROM 14.6.A.1.236)

Requirements:

Stock 14.6.A.1.236, unlocked bootloader, Recovery, fully and clearly uninstalled root

It's also better to check if SafetyNet Helper Sample successfully passes the test

https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

1) In fastboot mode flash modified boot.img from

http://xdaforums.com/showpost.php?p=68884579&postcount=3543

2) In Recovery flash modified Magisk-v6k.zip from

http://xdaforums.com/showpost.php?p=68884579&postcount=3543

3) In Recovery flash Systemless Root (either SuperUser or SuperSU - up to you) from

http://xdaforums.com/showpost.php?p=68034106&postcount=2

4) Install Magisk Manager from

http://xdaforums.com/devdb/project/?id=16532#downloads

5) PROFIT
[Magisk] KaMyKaSii:
As I am not familiar, I can not say anything, but it seems that's right. What I mean is that in my backup disregarded the block size parameter (in fact did not know existed), then the values ??at the end will go wrong. You will have to change in your code this:

dd if=/dev/block/mmcblk0 of=/cache/boot.img count=16777216 skip=30932992

For this:

dd if=/dev/block/mmcblk0 of=/cache/boot.img bs=1024 count=16384 skip=30208

But please, before attempting to flash, go to terminal emulator with super user permission, make the backup with the above command, and see if the file generated is actually boot.img as I said in my previous post (if it is a good sign, but if you use the header mtk probably your boot.img uses a compression not supported by Magisk, then better not flashing the modified zip (or yes, provided you have some way to install the boot.img stock in case of problems). And well, how you are using the explicit values for your device will not work in anothers devices. We expect topjohnwu make a script to identify the values of bs, skip and count of each particular device
[Magisk] ericotena:
[MENTION=4470081]topjohnwu[/MENTION] how can i install dolby atmos after i flashed the systemless v4a?
[Magisk] humzaahmed155:
I flashed magisk v6 on my OnePlus 3 (stock + running the blu kernel) and it hasn't made a difference as far as I'm concerned. Auto Magisk says I'm not rooted and the manager app says no root too. Ideas?
[Magisk] cadkey:
Read post #1 mate
[Magisk] humzaahmed155:
That's the first thing I did. Over, and over.
[Magisk] cadkey:
Works fine here mate
[Magisk] agentdr8:
Magisk by itself does nothing; you'll still need modules to make it useful. You'll want the phh superuser module that's made for Magisk, which is listed on the OP.

You'll also need the phh Superuser app from the Play store.
[Magisk] Goldnessel:
Hi,

some days ago, I installed Magisk and phh's superuser.

But since the last reboot, my system tells me, the su-binary needs an update.

And after this, checking the Magisk-Manager, the Root-Status ist *Not Rooted* and I can not toggle root anymore.

Does anybody has a new magisk ready phh's superuser?
[Magisk] krelvinaz:
Ditto on this. Apparently a lot of others are having similar issues.

I was able to fix it by

o Flashing Magisgk-v6.zip in TWRP

o Reboot back to recovery

o Flashing phh-superuser-17.magisk.zip

o then booting to system

The two APK's for magisk and phh super user are still on the phone. Just have to reauthorized the apps that need root and the Magisk app works fine.

There is some confusion of if busybox is even needed separately as that seems to be install already.

Not clear why a reboot causes the need for a binary update.

Nexus 5X

Android 7

Build: NRD90S

Other than that it works great.

Update: I don't have xposed and have never had xposed on this device since I got it.