yashsingh1/xdaforums huggingface dataset:
[Magisk] alroger:
And that's how you get the Root Toggle NOT to work. :D
[Magisk] matif525:
It's work in my devices, I don't have toggle problem.... lol (If I didn't flash that I can't get root access)

But maybe he shouldn't try to flash superuser.zip
[Magisk] SpL3rG3:
Anyone get this working with RBC Wallet in Canada? I've removed Root and root detetors show I'm unrooted; Magisk Manager says it has disabled root but my RBC Wallet app detects that I am rooted :/
[Magisk] xu3sno:
[MENTION=4470081]topjohnwu[/MENTION]

Will SuperSU for Magisk version be affected in the next Magisk update because of this:

http://www.xda-developers.com/supersu-privacy-policy-transferred-from-chainfire-to-ccmt/

Thanks.

Have a great day!
[Magisk] cubandanger05:
Working great on Nexus 5, Resurrection 6 ROM with systemless xposed. I confirm both Android Pay and Pokémon go work.

Edit: it is however weird that even with root disabled in magisk and android and Pokémon go working, other apps can still request root.
[Magisk] Captain_Throwback:
I'm pretty sure there's not going to be a "SuperSU for Magisk" version with the next update....
[Magisk] robert2103:
For 4.4.4 kk ? :( app manager , error de paquete

enviado desde algún lugar del mundo
[Magisk] Captain_Throwback:
5.0+ only is supported.
[Magisk] utbf:
Main Post is stating that this is not working for Sony devices. (I have xperia z5)

Is this still a problem?

Does anyone has experience with this or knows another way to hide root on sony devices?

Thanks
[Magisk] cubandanger05:
Here is a short video I just made. It shows safety net passes with root toggled off, shows PokÃ?Â©mon go working (I didn't let load all the way through for obvious reasons), system less xposed installed, and it shows apps requesting/working with root even with root "off". Unsure if root should work while being toggled off but it does so that's a plus for me. Here is the video [youtube]OXxEweRcr0w[/youtube]
[Magisk] Didgeridoohan:
[MENTION=5346465]Tulsadiver[/MENTION] Wouldn't it just be a matter of reverting the logic? Something like this (which is pure guesswork since coding really isn't my thing):

// Core only mode
if (access(DISABLEFILE, F_OK) [COLOR="red"]!=[/COLOR] 0)
core_only();

collect_modules();
[Magisk] Tulsadiver:
I'll give it a shot!
[Magisk] martyfender:
As far as I know, there is not yet a TWRP that is compatible with Android 10. You have to copy a stock boot.img to your device, patch it with the latest Canary Magisk Manager, copy that patched image to your PC then boot to bootloader mode and flash it to your device with fastboot. It is probably a good Idea to remove any modules you have first, as some are causing bootloops for users and it is hard to remove them later without TWRP and or root. Your best bet is also to do a clean install of Android 10 first where all of these leftovers will be gone, so they won't cause problems, such as the bootloops some have experienced.
[Magisk] Tulsadiver:
No, that didn't work either. I must be barking up the wrong tree....
[Magisk] jcmm11:
The code change looks correct (both versions actually, personally I'd just stick with commenting out the one line) so I'm not sure what's happening. Are you sure you're repacking correctly? Assuming you're using AIK [MENTION=4544860]osm0sis[/MENTION] is probably the best person to ask about packing questions.
[Magisk] MrCeez:
The yammer app detects root how can I bypass this.

I've already tried Magisk hide and package name change.
[Magisk] martyfender:
I would assume he would be using John's recommended build environment:
[Magisk] casouzaj:
Which device? I have Yammer installed in my Xperia Z5 Compact, running a stock based custom ROM. In my case, Yammer relies on MS Intune Company Portal. Both of them (and many other), as well as Magisk Manager itself, are hidden. I can only pass both Safetynet tests using the stable Magisk 19.3 version, along with the MagiskHide Props Config module (which, by its turn, requires the Busybox NDK one to work), and selecting my specific maker and model in the props command entered in a terminal emulator app.
[Magisk] Tulsadiver:
I just tried aik on Windows and the rebuilt image wouldn't boot the phone at all.

---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------

Yes

Edit:. At least to the best of my knowledge.
[Magisk] Dler Jarda:
Help
[Magisk] lividhen99:
With?
[Magisk] clumsyoxygen:
Just wondering now that topjohnwu has an Apple internship, will there be updates?
[Magisk] lividhen99:
Yup.

(this was before the official acceptance, but same idea)
[Magisk] martyfender:
His internship has been over for some time, as it was a summer internship. I assume he is back at the University of Michigan pursuing his Masters studies.
[Magisk] BillGoss:
Silly question, possibly, why not simply create the disable file (/cache/.disable_magisk or /data/cache/.disable_magisk) before booting instead of trying to modify Magisk itself?
[Magisk] ktmom:
You would have to read back to the begging of that journey. Basically A10 update, no working TWRP. Previously installed modules causing bootloop when Magisk is installed. I think I would factory reset by now.
[Magisk] jcmm11:
Yes, and apparently it seems to be building fine. In which case the build part isn't the problem.

He's then, I think, unpacking a kernel already patched with Magisk and attempting to replace init with the changed version. This part of the process would be outside of the normal build environment.

One huge caveat with everything I'm saying, I haven't done anything along these lines in a VERY long time so I might be off on some particulars, but I'm not totally clueless here either.

From what I know AIK should work for this final part.

So I decided to play a bit. I took a Magisk patched stock kernel from my Pixel 3 XL and used the mobile version of AIK to unpack, then repack, the kernel. I then flashed the kernel and rebooted successfully. If init was compiled correctly it should be easy to replace init and repack the boot image.

[MENTION=5346465]Tulsadiver[/MENTION] What phone do you have? I think I saw you in the Pixel 3 XL TWRP thread so if that's what you have (or just a Pixel 3, common kernel between them) let me have the compiled init and I'll see if I can repack the kernel.

Don't know why you're having issues with the Windows version of AIK, although osm0sis says that there seems to be a lot of user error with that version. Did you add sudo.exe to Windows Defender?

Edit: Android 10 and latest Canary
[Magisk] Tulsadiver:
Here is the last one I compiled. It isn't really zipped, just renamed.

Yes, I have a Pixel 3 XL.

Edit:. I haven't been experimenting on my Pixel 3 XL. I've been using my Pixel 2 for testing.
[Magisk] Wesley_NL:
i cant install the packages or app i keep getting this error message when i download via magisks and on the wesite there is not a updated version

sm-g965f stock rom / kernel
[Magisk] Didgeridoohan:
https://didgeridoohan.com/magisk/Magisk#hn_Problem_parsing_the_package
[Magisk] heynando:
Well I didn't know only mounting as rw would trigger the tamper detection, but yeah you're right!

It's A/B , I did follow but there might have been a couple of apps that mounted /rw even though I didn't ask them to.

What does it mean to remove -w and How do you do it?

Yeah I do that too, but if you act like me allowing root access to a few poorly designed apps, they might end up mounting /system as RW just to test their level of access and then adios OTA

Is TWRP capable of installing the .img of each block extracted from the firmware whilst IGNORING the tamper protection?
[Magisk] jcmm11:
I repacked the image with no problem but it boot loops on me.
[Magisk] Ch3vr0n:
By default 'preserve dm-verity' wasn't enabled for me on Pixel 3xl, causing the bootloop.

Check it's enabled under 'advanced settings' before you patch the boot image. After that it worked first try for me

1. Grab canary manager

2. Set update channel to canary

3. Check advanced settings for both 'keep encryption' and 'dm-verity'. Both must be enabled

4. Patch boot image

5. Flash through fastboot, done.
[Magisk] Tulsadiver:
Yeah, mine wouldn't boot with it either.

I have some files l grabbed for Linux that will work on my old PC that I have as a dual boot, linux-windows. It is done in stages, it seems. It only completely recompiled the ramdisk leaving the other two intact. The ramdisk is where the init file is so that is all I need. It recompiles fine. It boots fine afterwards. Just doesn't boot core-only.
[Magisk] Sterium:
It's normal on open magisk manager slide fast two tab?

[YOUTUBE]https://youtu.be/CSUviged1jk[/YOUTUBE]
[Magisk] martyfender:
No, that is not normal. Do you perhaps have a mod or launcher installed that could be doing this?
[Magisk] Sterium:
never mod... miui stable pie on mi note 3
[Magisk] jcmm11:
When you download and unzip the factory image you get a number of files including another zip file (contains boot image + other img files, system, product, dtbo, vendor etc) along with a radio image and bootloader image. You also get some sh and bat files which you need to run to install the update.

If you open flash-all.sh/bat (depending on your OS) you'll find at the end

fastboot -w update <current update name>.zip

The -w tells fastboot to wipe the data partition (including /sdcard) so if you ever run this with -w make sure you backup all your personal data first. The update command also forces a reboot when it's done and I usually don't want that so I change the line to

fastboot --skip-reboot update <current update name>.zip

and then follow it with

sleep 5 (in the sh file, the bat file uses ping to force a wait)

fastboot --slot all flash boot Magisk.patched.img

Note that when I first updated to Q I did a clean install (wiped data using TWRP on Pie first) the phone wasn't happy doing an initial boot with a Magisk patched kernel so I let the phone boot to the starting setup screen first (using the untouched stock kernel) then forced it back to the bootloader and flashed the Magisk kernel. It's been fine since. Updating from the Q beta to Android 10 final I included the patched kernel, as above, and had no issues.
[Magisk] zgfg:
Sorry if missunderstanding - did you try to build Magisk v15.3 (or Canary v15.4) installation to automatically start Magisk in Core only mode?

It would be of general interest, not only for Pixel/Q, and I was akin to give it a try.

So, was your attached magiskinit a zip file to be patched over any Boot/Ramdisk image (not already a patched Boot image for your particular phone)?

I just downloaded magiskinit.zip and from magisk Manager, Modules, tried with + (this way an existing Boot/Ramdisk image shall be re-patched by another Magisk version), but it failed
[Magisk] Tulsadiver:
Sir, I got this one to boot but still not core-only. I used magiskinit64 instead of magiskinit.

Edit: Finally got it to work. I appreciate everyone's comments and suggestions. It was a combination of wrong init file and unpacking and repacking the patched IMG. Here is a magisk core-only bootable file for Pixel 3 XL.

https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
[Magisk] don_monton:
alarm not working at 19.3

After updating magisk to 19.3 (from 17.3) my alarm stopped working. I also can't receive some SMS's.

Phone: Huawei P8

ROM: Magic Arrow
[Magisk] jcmm11:
Just a note that since they have a common kernel it should also work on the non-XL Pixel 3
[Magisk] Tulsadiver:
Thank you for your help!
[Magisk] cristianodk:
After installing the magsik 19.3v, the phone (moto z play version oreo 8.0) is in bootloop, can anyone help me?
[Magisk] dnsmo:
i lost root from time to time in my pixel 3 xl andriod 10. I used the flashboot flash command. anyone else also seeing this?
[Magisk] drothenberger:
When you say "no working TWRP", do you mean you can't fastboot boot TWRP at all, or do you mean it won't decrypt data? You don't need to TWRP to decrypt data to touch the file that enables core-only mode, but you do need to be able to boot TWRP.
[Magisk] Tulsadiver:
You can boot TWRP but it doesn't mount/read storage or system.. You can't touch any files because it doesn't see them.
[Magisk] drothenberger:
Have you tried? I don't think /cache or /data/cache are encrypted. I tried this on 9 by starting TWRP and not letting it decrypt; I could touch /data/cache/.disable_magisk and it did in fact trigger core-only mode.
[Magisk] Tulsadiver:
Yes
[Magisk] zgfg:
Actually, Magisk Canarry b19309 just released, and from Changelog:

> > Allow removing modules without root in ADB shell by magisk --remove-modules. Useful when stuck in bootloop and have access to ADB (99% of the time)
[Magisk] Tulsadiver:
Cool!
[Magisk] martyfender:
Entering magisk in the adb shell gives all available options. some options require a root shell, for example:

marty@marty-Inspiron-570 ~ $ adb shell

shell@NX16A8116K:/ $ su

root@NX16A8116K:/ #
[Magisk] creeve4:
What is the correct method for re-flashing magisk after updating a ROM on an A/B device?

When flashing the ROM, it flashes to the inactive slot. How do I get magisk to flash to the inactive slot in TWRP after flashing a ROM?
[Magisk] ktmom:
Reboot back to recovery should switch slots after a ROM flash.

I personally boot the ROM and do any setup then return to recovery and flash Magisk. That way if there's a problem with the ROM flash, it's not compounded by flashing something else. Also, if after flashing Magisk and it bootloops, I know that the ROM booted fine first.
[Magisk] beardymarrow:
After updating the rom, Install to the Inactive partition using magisk manager, before rebooting.
[Magisk] creeve4:
Thank you for the advice.

Is there anyway to get magisk to install to the inactive slot in TWRP, so I can flash magisk immediately after flashing the ROM (before I boot to system) and without rebooting to TWRP just to flash it?
[Magisk] jhpdroid:
Magisk install function includes this
[Magisk] jhpdroid:
Doh!
[Magisk] jcmm11:
TWRP includes a switch to enable you to choose the slot. It defaults to the active slot but you can switch to the other one.
[Magisk] JudgeDread11:
Possibly caused by a battery saving app or Android battery optimization killing magisk manager. Make sure you exclude it from these.
[Magisk] dnsmo:
I only had the stock andriid. And don't see the option to exclude the app
[Magisk] jcmm11:
Settings|Apps &notifications|Advanced|Special app access|Battery optimization

(Or just search for Battery optimization from settings)

Once you get there choose "All apps" (default is "Not optimized", find the app, change it to "Not optimized"
[Magisk] martyfender:
Settings, Android, battery, right drop down menu, battery optimization, see my screen shots.
[Magisk] dnsmo:
I figured it out too thanks. This never happen on 9. Don't know what happen now.
[Magisk] Duckapple:
Legacy uninstallers?

Is there some location to access older uninstallers?

My current TWRP/magisk setup doesn't work, as I haven't updated anything (yes, even OS) in over a year. It fails with "unknown image format" with the current uninstaller.

I'm using a OnePlus 5, Magisk 16.7 and TWRP 3.2.3-0 cheeseburger
[Magisk] daniele62:
App2sd : which path I have to set in the preferences to mount 2nd partition at boot?

In app2sd there is a setting which read: Use this option to set su.d/post-fs-data.d/service.d path (full path) of your super user management app......

Where is these folders in for Magisk 19.3?

Thanks.
[Magisk] martyfender:
/data/adb/post-fs-data.d/

/data/adb/service.d/

I use the service.d custom path with Apps2SD.

Those locations are where boot and startup scripts are placed. See topjohn's Magisk documentation for what each location does as far as the loading order of the scripts:

https://topjohnwu.github.io/Magisk/guides.html#boot-scripts
[Magisk] jcmm11:
Other options are to use unsu from osm0sis or to do the job manually. For manual uninstall:

Uninstall Magisk Manager then boot to TWRP.

Remove all the contents of /data/adb

Flash an unrooted kernel image. I recommend doing this last step no matter how you uninstall. If everything is correctly in place then the uninstaller will automatically do this, but if a backup isn't there this won't work, so it's safer to always do it yourself.
[Magisk] NMe84:
Is there anyone who recognizes this at all or am I on my own? I'm not sure which part of my setup could even cause this so it's difficult to search for solutions.
[Magisk] BillGoss:
I had absolutely no problems installing Magisk on 9.0.5. So, I would:

1. Uninstall Magisk and then, because you want to make sure you're 9.0.5 installation works properly...

2. Flash stock 9.0.5 rom

3. Flash the modified firmware

4. Reboot your phone (you'll lose TWRP) and make sure it boots up cleanly.

If all is good, then:

5. Flash TWRP in fastboot

6. Boot directly into recovery

7. Flash Magisk

8. Reboot your phone
[Magisk] jcmm11:
I really think that in this case you'd be better off asking for help in your device/ROM thread.
[Magisk] syde1020:
Nevermind. I'm a moron
[Magisk] wilsonhlacerda:
/data/adb/service.d

Use it. This one triggers on boot always when Magisk is loaded, no matter if on Core Only Mode or not.
[Magisk] jazef1:
Im having issues installing Magisk on my rockchip 3399 tablet. It already has root access however on direct install I continue to get this error "Unknown boot img format" and aborts the installation process. can someone please assist... maybe Ive forgotten something?
[Magisk] zgfg:
If phone does not boot (and if there is no TWRP for that phone), then one must ask somebody else to patch Boot/Ramdisk for him or must patch himself on another phone

Hence, does it work to patch Boot/Ramdisk image for the phone A by Magisk Manager on the phone B (A and B differnt phones/firmwares) and then to flash that patched image to phone A?

Edit - seems it works, just tested the following:

Installed Magisk Manager to Huawei Mate 9 with stock Pie (EMUI 9).

Mate 9 not rooted, even Bootloader locked

On Mate 9, patched Huawei P9 Oreo b540 (EMUI 8) stock Ramdisk and then flashed that patched image to Huawei P9 b540:

P9 booting ok

Root working ok

Tested BusyBox and YT Vanced modules, both working fine
[Magisk] NMe84:
Sadly that's exactly what I did, thanks though. I'm starting to feel like my only way out of this mess is flashing the OTA and then factory resetting the phone so I don't need the modified firmware. I'm not sure how much good that will do me though.

I'll give that a go before doing a factory reset. Thanks.
[Magisk] imska:
Hey, I would like to know if flashing magisk on a freshly unlocked device also automatically disables dm-verity and/or force-encrypt.

Does anyone know if this is included in the magisk flashing zip or if I have to flash the dm-verity disabling zip for relevant devices?

Any hint is greatly appreciated!
[Magisk] pac213:
Hi There,

Magisk hide doesn't work for this app. Even installed magiskhide prop and enable it, the app still detects my phone as rooted. This is a banking app and I may need to revert myt phone to stock.

https://play.google.com/store/apps/details?id=ph.com.psbankonline
[Magisk] zgfg:
Please consult Magisk Installing guide.

If installing by TWRP, you can use options: KEEPFORCEENCRYPT=true (or false) and KEEPVERITY=true

But it's easier to patch the Boot image from Magisk Manager, and to check/uncheck corresponding options before patching
[Magisk] imska:
Thanks for your response.

Consulting the magisk installation guide, I think I need to be more precise, because I am not sure about how force-encrypt and dm-verity works. I never had a device where this would matter, but I would like to make devices where this is relevant work with my one-click custom rom installer.

The procedure for an installation starting from stock boils down to:

unlock bootloader

flash/boot twrp

check if /data is mountable and not 0mb in size (if so, format /data and reboot into twrp)

clean flash rom, magisk and nanodroid stuff

What consequences will formatting /data have on the magisk installation afterwards with regards to dm-verity and force-encrypt? And does any of this have something to do with encryption mechanisms of custom roms like LineageOS or RR?
[Magisk] Kockowan:
]Hello,

there is a problem after flashing Magisk-19.3 to a Carbonrom-6.1 (Android-8.1) on a Sony Xperia-Z3compact:

TWRP-Recovery (v3.2.1 or 3.2.3) works, booting of normal system is possible, rebooting to TWRP works too. BUT:

If flashing Magisk-19.3 (from Magisk-18.1), furthermore only booting to recovery itself ist possible, NOT to CR-system. It seems system isn' t present...

Recovery of backup is necessary.

So why brakes installation og Magisk-19.3 TWRP-recovery and/ or booting of normal CR-system?

Thx for any hint, best regards!
[Magisk] seb21:
Hi all.

After rooting with Magisk i have no voice output in Google Assistant and Google Maps.

The device is Joying SC9853i Head Unit (Android 8.1). Root method (only available) is patching boot image.

I know that only changed file is init , but it is binary ,so hard to compare with the original. Don't know it is normal that patched init is smaller than original file 633kB vs 1800kB.

Can someone tell me how exactly Magisk change the system ? Is the init file patched or it is a new rooted version ?

I'm out of ideas how to fix this issue. Voice responses is needed in car unit, but root makes the life a lot easier.

So please, has somebody idea how to approach this problem ?
[Magisk] casouzaj:
I'm running the latest CR7.0 release (dated 0819) in my currently spare Z3C phone, with TWRP 3.3.1-0.3 (from NeoArian) and Magisk 19.3 is the only version which, along with the MagiskHide Props Config module (which, by its turn, requires the Busybox NDK one to work), allows me to pass both Safetynet tests. Moreover, I have to run the props command on a terminal emulator app (just once), and fetch my maker (Sony) and model (Z3 Compact) and answer yes up to the reboot step.
[Magisk] pac213:
ANyone have any ideas?
[Magisk] Aaagogo:
Device: Redmi Note 7

Rom: MIUI Global 10.3.6.0 PFGMIXM

Currently installed:

Magisk 19307

Magisk Manager 232

there was an issue updating to 19309 and 234

error message of "There was a problem while parsing the package" for both updates.
[Magisk] guest4711:
Unhide MagiskManager (which will download and install the latest version), set update channel back to "stable" if desired, update Magisk, hide MM again. Set update channel back to " stable" if desired.

Discussed a lot here and in canary thread...
[Magisk] Aaagogo:
thank you very much,

it was weird, previous updates did not require unhiding...
[Magisk] Didgeridoohan:
Usually I try to test these of cases, but the app isn't available for me. There are plenty of tips and tricks to try out here though:

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

Previous versions did not have that bug...
[Magisk] Sturmkater:
Magisk can't find himself after hiding

Hi, I tried to unhide and hide magisk in order to get the test passed, but since then he cant see him self and want me to reinstall. I can download the zip, but installing brings me an error.

I can't ad attachments:
[Magisk] Didgeridoohan:
The Magisk db probably didn't register the new package name. Try to uninstall any Managers (there might be several) and install the apk again manually.
[Magisk] Suvorik1969me:
Which Magisk i can use with Android 10 rom ?

Device - whyred.

ROM - LineageOS 17.0.
[Magisk] pac213:
This worked for me. Thank you!
[Magisk] guest4711:
Try canary.
[Magisk] Kockowan:
Regarding https://xdaforums.com/showpost.php?p=80244118&postcount=35700 :

Any hint, why updating Magisk-18.1 > Magisk 19.3 has broken TWRP-recovery in CarbonRom-6.1 (=Android-8.1) on a Sony Xperia Z3c? How to solve this issue, how to get back recovery?
[Magisk] casouzaj:
What CR6.1 build are you running? There was an issue with that ROM regarding the issue you are facing, but it had been fixed in build dated 0611.
[Magisk] Kockowan:
Sony Z3c-update has been done as following:

TWRP-3.2.3.0 working

CARBON-CR-6.1-NOCT-RELEASE-z3c-20181211-0850

Magisk-18.1

>>>

CARBON-CR-6.1-NOCT-RELEASE-z3c-20190911-0529

Magisk-19.3

Now TWRP-recovery is broken, no more access. Always CR system is booting. Further installation of newer Magisk or CR is NOT possible.

How to solve this issue?

Thx + regards!