yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
In Mixplorer, you can open the archive, higlight the file inside, then click on the info button on the upper right, where a dialog opens, click on hashes and it calculates hashes for: all types:CRC32, MD5, SHA1, SHA256, SHA384 and SHA512. For me, the SHA1 checksum matches the checksum in the file name, So I don't have to actually unarchive it to check it. Maybe others do it in different, or better way, but I have never tested them, Since I use Mixplorer.

Is there a stock rom available for your device? If so, (which I would think so with Motorola), I believe you should be able to extract the boot.img from It? That would be my number one choice over using the one backed up by Magisk.

I, however, don't know how Motorola does it.

UPDATE: When I search for: Moto Z2 Play stock rom, I find plenty of listings for it here on xda and other places. Being a glutton for punishment, I was able to download and extract an Oreo version of the rom's, boot.img: albus-user 8.0.0 OPS27.76-12-25 26 release-keysM8953P_41.50.07.63R I'm not sure what version you have, but you should be able to do that for your own version.

---------- Post added 22nd December 2018 at 12:05 AM ---------- Previous post was 21st December 2018 at 11:44 PM ----------

I have 5 devices, with both Canary and Unofficial builds, and I also saw this recently in one of my logs. Have you tried opening said root apps a second time to see if you get a root prompt, the second time?

I believe I saw this with apps that I have that have apply on boot settings, such as Kernel Adiutor, Lspeed, and Apps2SD. I have not had this happened again, since both Canary and unofficial builds have newer commits by [MENTION=4470081]topjohnwu[/MENTION] , than the released, v18.

---------- Post added at 12:09 AM ---------- Previous post was at 12:05 AM ----------

In that screenshot, I see you are not connected to the internet. How can you update when you are not connected to the internet? Also, there must be some problem in translation, it is not clear, 100%?

What is: "face app keep stopped"? Do you mean Facebook has stopped? That, I think, is may be unrelated to Magisk.

And, of course, you made no mention of your device and Android version. "M on resurrection remix 5.8.4" doesn't give us much info. I did determine that it is based on Nougat, though.

Why do rom makers incorporate Magisk into their ROM's? it is only asking for trouble down the road. Maybe the Magisk uninstaller will help you in this case? I would usually suggest a flash of a clean boot.img in this case, but since the ROM already has Magisk v13, that RR boot.img probably was patched by the old version of Magisk, also.
[Magisk] The Analog Kid:
[MENTION=8126387]martyfender[/MENTION] yes, I already tried the MIXplorer (you can see screenshot attachments a few comments above) and I already have backup for boot.img as well; but I found interesting to give the Magisk copy a try cause it is already in my phone. In any case, my goal is to be ready with all the necessary stuff on hand just in case installing v18 update also fails on my side. I like being one step ahead... BTW, if worth something, by using "RAR" app I was also able to know the reason why my Magisk copy is corrupted (see attachment). Thanks for the support on this matter.
[Magisk] jcmm11:
Did you try to repair the img file? That will never work. That's primarily for rar files with some use for zip files.
[Magisk] The Analog Kid:
Yeah I know; I did just to know what it'll throw. You can't blame me for that...
[Magisk] NiEb:
mee too !

Samsung A3 2017

a few hours it works, then false safteynet
[Magisk] Zedoki:
Yes, each time I have a magisk stub that ask me to install the "original" magisk apps so I'm always declining.

If I agree, I have both apps and it's detected by Pokémon Go for instance.

Edit: the issue is solved for the moment.

Probably had an old version of the packet.

So I uninstall everything and install back the original one. And hide the packet again. Working now.

Thank for the advice!
[Magisk] futureshock:
With magisk18 I can't use adaway... It can't write hosts file.. downgrade to 17.3 and it works again
[Magisk] guest4711:
You have to enable systemless host on new Magisk Manager and reboot before trying to use AdAway. Nowerdays systemless host is a regular Magisk Module (not a toggle in MM and implemented in MM as before). The module is not enabled by default, so after selecting "systemless hosts" in MM it will be active after reboot.
[Magisk] futureshock:
Thx I found it now
[Magisk] Nebrassy:
Yup, RAR is made by rarlab, creator of Winrar
[Magisk] hubab:
Hi OP,

I'm on Samsung Note 8 - Light Rom and im having issues with Modules.

It installs correctly but doesn't show up in installed apps.

Here's what i tried to fix the issue :

- Re-install Magisk through TWRP + wipe cache/dalvik => didn't solve the issue.

- Uninstall Xposed via Xposed uninstall (i thought it would create a problem) + wipe cache/dalvik + Re-install Magisk => didn't solve the issue.

- Uninstall the Magisk

Wipe cache/dalvik

Reboot system and the back to recovery.

Re-install properly Magisk via TWRP.

Re-install a module (Youtube Vanced for ex.)

=> didn't solve the issue either but now i have 2 Magisk app installed : Magisk Manager and "Manager"

Im out of ideas and diagnosis...can you help plz?

At the beginning i thought it was related to a specific module but i tried install another mod and its the same issue.

If you want a log please lemme know which one so i can provide it.

Phone : Note 8 (N950FD)

"Magisk Core Only Mode" => unabled

Android version LightRom Oreo (8.0)

Magisk version : V 18
[Magisk] martyfender:
"unabled" Do you mean disabled, or enabled? If core only mode is enabled, that is one reason the modules aren't showing up.
[Magisk] hubab:
Yeah I meant that it's disabled.
[Magisk] jcmm11:
Does the Rom you're running have Magisk pre-installed?
[Magisk] hubab:
Yeah it got Magisk pre-installed but I read somewhere where OP said that it might be not the good one and since my problem wasn't getting solved I tried to uninstall magisk and reinstall through TWRP.
[Magisk] martyfender:
My experience in the past, on an older device, was that the xposed uninstaller didn't seem to revert all changes and I ended up re-installing my rom to get it back to normal. That was on a device with Android 5.1.1.

When you uninstalled Magisk, did you use the Magisk Uninstaller.zip in TWRP and then flash a stock boot.img before reinstalling Magisk?
[Magisk] the_alien:
I'm trying to get Magisk running again, seems like I made an error and installed the TWRP App, this causes a bootloop. Thanks TWRP! Any way to get rid of this app? Haven't found any helpful informations on this.

12-22 16:51:33.372 2827 2827 D AndroidRuntime: Shutting down VM
12-22 16:51:33.373 2827 2827 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
12-22 16:51:33.373 2827 2827 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {me.twrp.twrpapp: android.permission.READ_PRECISE_PHONE_STATE, me.twrp.twrpapp: android.permission.BATTERY_STATS, me.twrp.twrpapp: android.permission.PACKAGE_USAGE_STATS}
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2005)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:89)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.systemReady(PermissionManagerService.java:2052)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21280)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.SystemServer.startOtherServices(SystemServer.java:1708)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.SystemServer.run(SystemServer.java:437)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.server.SystemServer.main(SystemServer.java:296)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
12-22 16:51:33.373 2827 2827 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
[Magisk] hubab:
Yeah it might be the last solution and I wanna avoid it if possible...
[Magisk] martyfender:
What is your device, Android version and Magisk version?

Did you flash a TWRP image to your device, or did you just install the app from the playstore? TWRP is not an app but a custom recovery that replaces the stock recovery on your device, if one is available for said device?

I believe the Playstore app will download TWRP and install it on officially supported devices, only. For many devices, third parties have built TWRP for them. These must usually be obtained elsewhere. And of course, they are not built for all devices.
[Magisk] the_alien:
Pixel (sailfish), Android 9 (december patch), Magisk 18.

I installed the TWRP zip through a TWRP that was booted through fastboot and there was a prompt once to install the app, I don't know what I selected, but as far as the log tells it was 'yes'.
[Magisk] martyfender:
Personally, I have always unchecked the option to install the app, so I have never installed it as my devices have TWRP built by a third party so the app would not be useful to me.

If your Pixel is a type A/B device, [MENTION=4470081]topjohnwu[/MENTION] recommends keeping the stock boot/recovery image installed and only temp booting TWRP through fastboot, from a PC, before installing the Magisk.zip

See his Dec. 4th post on his Twitter blog for details:

https://twitter.com/topjohnwu
[Magisk] the_alien:
Yeah, I'm trying to do this right now, I already removed the TWRP and reflashed stock boot.img, but for some resason when flashing Magisk 18 from a temp booted TWRP, I end up in the same stupid bootloop mentioning the TWRP app.
[Magisk] martyfender:
Maybe someone else has an idea, but I would suggest you get help in you device forum, because someone that has your device may know why this is happening. I have never heard of this happening. Are you using the latest TWRP available for your device?
[Magisk] jcmm11:
You're going to need to, via TWRP, go into the system partition, in either app or priv-app, and delete the Magisk Manager directory. That's why you're getting 2 managers. Unhide the one Manager (the one that's just named Manager) and run the uninstaller first.
[Magisk] @srmahunt:
Hi, i have installed the magisk v18, and some of the apps have problem detecting root, anyone else having this issue?? Any fix for this??
[Magisk] hubab:
You mean the magisk uninstaller zip?

And once I've uninstalled, what's the nexg step then?

Thanks again for helping me.
[Magisk] ChrisG12:
Pixel 2 XL bootloops to TWRP after installing Magisk

I recently purchased a Pixel 2 XL (Google version). I've unlocked the bootloader and installed the latest full factory image for the Dec 2018 release of Pie. With the factory image and TWRP (3.2.3.1) installed the phone seems to work. As soon as I install the Magisk zip through TWRP and try to reboot the phone hangs on the G screen with a progress indicator. After a while it will reboot straight to TWRP. If I then uninstall Magisk (using the Magisk uninstaller) the phone works fine (though without root obviously). I've tried both Magisk v18 and v16.7. I've also tried setting the KEEPVERITY=true and KEEPFORCEENCRYPT=true flags before installing Magisk. I've tried multiple reboots, wipes, re-installs, etc. But the phone only boots to TWRP if magisk is installed. I've attached the magisk and recovery logs (taken right after the bootloop dumps me into TWRP). Any suggestions would be greatly appreciated.
[Magisk] Demonday123:
I already tried many times opening root apps still can't get a root prompt. Also, I installed Root Checker, it said "Root Access is not properly Installed" although Magisk v18 already installed. Yesterday, I try flash SuperSU by Chainfire it worked and have root access. All Root Apps worked but too bad can't hide root from banking app. Do you have any solution can help me to fix this error? [MENTION=8126387]martyfender[/MENTION]
[Magisk] Nebrassy:
The problem is caused by twrp, restore stock boot image and fastboot boot twrp then flash Magisk, don't flash permanent twrp
[Magisk] Badger50:
Not always true. I flash magisk frequently with permanent twrp. Sometimes you just need to flash the magisk uninstaller followed immediately by flashing the magisk zip :good:
[Magisk] Nebrassy:
Is that also on the Pixel 2 XL?
[Magisk] Badger50:
Yep, that's my device. You a Husker fan? :laugh:
[Magisk] Nebrassy:
Nope it's just my actual name :D
[Magisk] Badger50:
Very nice! Great name bruh! :good::good:
[Magisk] ChrisG12:
Ok I tried installing the Magisk "uninstaller" zip and then immediately installing magisk v18 zip. Same problem as before - G screen hangs for a while and then bounces me to TWRP. Note that TWRP otherwise seems to work (as long as Magisk is NOT installed).

Also tried flashing factory boot image to remove TWRP ("fastboot flash boot_a boot.img" as well as boot_b) but this just leaves me with an android guy on his side with the words "no command" when I try to go to what should now be the stock recovery...
[Magisk] Wolfcity:
Normally the stock recovery should be named something like recovery.img. So you have to

fastboot flash recovery "exact-name-of-stock-recovery.img" to get rid of TWRP.

And I think the factory boot image should be named boot.img or similar, not bootloader.img.
[Magisk] Nebrassy:
That is the stock recovery, you just press power + volume up at the same time to get the options, now just fastboot boot twrp and flash Magisk zip
[Magisk] Badger50:
That is what the stock recovery looks like. Try this,

Fastboot into twrp, then flash the twrp installer zip and let the OS boot up. Then go back to twrp and flash magisk twice.
[Magisk] jcmm11:
Not true on a/b devices. There is no longer a separate recovery partition. Recovery is the ramdisk in the boot.img

It's also why, if there's a problem, it's important to start with a clean boot image.

Which is why, if you're going to install TWRP to the phone, you need to first boot to recovery via flashboot using twrp.img then install via the booted TWRP using twrp.zip

It's also one reason why topjohn recommends against installing TWRP to a/b devices and suggests just booting to it via fastboot when you need it.

You are correct about the boot image name
[Magisk] ChrisG12:
First I'd like to say thanks for all the folks helping on this...

Okay - so here is what happened:

- Fastbooted to TWRP

- From TWRP installed the TWRP zip

- booted to OS, then booted to TWRP

- installed magisk zip twice (without leaving TWRP).

- let OS boot

Same problem: Stuck on G screen for a minute or so then automatically reboots to TWRP
[Magisk] jcmm11:
Make sure MM isn't hidden.

Flash uninstaller

Remove MM from /system

Wipe dalvik

Install Magisk

Save recovery log

Reboot

Hopefully that'll do the trick.
[Magisk] varadinum:
only root without twrp

Hi,I have a Samsung Galaxy A9 (2018) SM-A920F. This is my first Samsung.TWRP does not exist yet. I want to root it with Magisk. I need to flash the Magisk manager patched boot img with odin.

I can not find the file boot.img. Magisk manager installs but boot.img I can not patch. Where can I find the boot.img? In which directory? Media? Dev? Etc?...Where can I download boot.img?

I have already downloaded the original firmware. I can not find Boot.img.

Please, can someone help me?
[Magisk] nansah:
I just switched from SuperSU to Magisk but Xposed installer says the framework is not installed even though greenify & all the other modules detects the framework & never had this issue with SuperSU.

So I was searching online as to what is going on & someone recommended that, I should use the installer to reboot my OPO device with LOS 15.1 before the framework can be detected.

I tried to do exactly that & the error in the picture is what I'm getting.

Magisk superuser access is already granted & root checker apps all confirms that my OPO is rooted but just can't reboot with Xposed.

Pls any help or suggestions will be very much appreciated as I've searched online to no avail.

Thanks in advance!!!
[Magisk] martyfender:
Did you use the Magisk module for xposed, or did you install xposed to the system? With Magisk it is recommended to use the module because it is systemless and does not modify the system.

Also, if you were previously rooted with SuperSu, did you first flash UnSu.zip first to completely remove SuperSu, first?

---------- Post added 23rd December 2018 at 12:19 AM ---------- Previous post was 22nd December 2018 at 11:54 PM ----------

Disclaimer, I do not own a Pixel device but here is something you can try, based on my own personal experience with my devices, which are not A/B devices. Make sure you have a fresh stock boot/recovery image installed. temp boot TWRP from your PC with fastboot. do not add the flags for dm_verity and forcencrypt. choose wipe, factory reset then swipe.

Do not reboot first

. Next flash the Magisk.zip and then reboot. The data partition has been wiped so the first boot may take some time and be stuck on the boot animation for a while so be patient. It can take several minutes for a new, unencrypted data partition, to be created.

If all goes well, you will boot to the android setup screen where you will setup the device as new.

Before doing this, make sure you have backed up any important data. Since you started with a factory image, I would not hope you have anything yet important to loose.

Another disclaimer: I would wait for someone with the device to post here first, as I may be way off base for this type of device. Some also may feel uncomfortable running unencrypted. However, there is supposed to be less overhead running unencrypted, therefore the device should run faster?

I just know that this method, with a decrypted data partition has worked very well for my 5, Nextbook Ares 8A's, with Android 6.0.1.

Because these devices have a separate recovery partition, I eventually installed TWRP, but the initial backup and setup was done by temp booting TWRP.

The manufacturer never released roms, so I depend on this initial backup as my factory rom.

I the above does not work, I would suggest trying either Magisk v17.3 beta, or the latest Canary build. The Canary build works great on the two devices I have it on.
[Magisk] cmch:
Having some minor issues with magisk sometimes a popup appears that magisk stopped working and when i try to open the app it hangs and prompt me to close the app or wait

Im giving

Magisk logs
[Magisk] martyfender:
I congratulate you on at least providing a magisk.log. but what is your device, Android version and custom rom version? From your log, it appears to be los. Have you tried something simple, such as downloading the Magisk Manager, uninstalling your current version, then reinstalling the downloaded version?
[Magisk] hubab:
I checked and there's no MM in /system.

The both MM are found in data/app.

Should I still do the steps above?
[Magisk] guest4711:
Double check that no MM is in /system/app nor /system/priv-app (after flashing uninstaller. If you check this from within TWRP make sure your /system partition is mounted.) Then flash Magisk.zip and reboot. (You may include the other steps too to create a reasonable log.)
[Magisk] ktmom:
The boot.img should be in the compressed file that begins with AP from the downloaded firmware file. This thread, although for a different Samsung device, should give you some insights.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] hubab:
I double checked in /system/app and /system/priv-app...there's litteraly nothing concerning magisk manager. I also tried to look another app where the apks are located and they're both located in data/app.

So once uninstalling the MM, should I also delete theses 2 folders?
[Magisk] guest4711:
Yes. You will probably loose some settings (theme, timeout time) but all relevant data (magisk hide settings, modules, root settings) are stored outside this folders.
[Magisk] hubab:
So I did the steps above + deleting both MM from data/app.

Once the MM installed I retried to install a module (yt-vanced in my case), restarted the phone but still can't see it in the launcher (neither from settings).

Here's the recovery log, magisk log etc.

Thanks in advance for your help.
[Magisk] danzukuka:
i just installed magisk 18 on my phone through twrp recovery and everything looks great, magisk is installed manager is installed, all of the non-terminal based modules work great but no app recognize root privilage. in magisk manager superuser section it says no apps found and i cant do anything in terminal.

my phone is xiaomi mi 4i and im on miui 6.5.3.0 android 5.0.3
[Magisk] fmotta:
Same is happening on Xiaomi mi Mix 3 with global rom...
[Magisk] kidpunk:
Is busybox still needed/recommended to be installed if using Magisk ? Not sure if they cover the same functions..
[Magisk] martyfender:
Magisk has its own, built in busybox for its functions, but if you use apps that depend on busybox, I would recommend installing the module: Busybox for Android NDK, to install it systemlessly.

---------- Post added at 04:32 PM ---------- Previous post was at 04:28 PM ----------

Try reflashing Magisk 18 again over what you have, to see if to see if that solves it.

If not, try flashing the latest Magisk Canary debug build, because you can provide more verbose logs with it, if you still have the same problem.

If you are on the Canary build, you can post logs in the issue area on [MENTION=4470081]topjohnwu[/MENTION] 's github page.

However, if you don't provide logs, your issue may get closed without a possible solution.
[Magisk] cmch:
I was thinking about reinstalling magisk and all reflashing all modules lets see if problem still persists or not

Btw im in rr rom oreo in redmi 3s

---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------

Busybox module works better now a days
[Magisk] cmch:
Having same issue even after full uninstallation and reinstallation now what to do?

Saw some errors in logs check it out

Network error sorry cant upload logs dont know why but

Write failed with 32 : brokem pipe something like that
[Magisk] @srmahunt:
Any comment on this??
[Magisk] xunholyx:
Upload the logs to Dropbox or something similar and post the link to that here.
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHelp

I would suggest installing the latest Canary debug build so you can provide more verbose logs and also to see if it solves your problem.

If not, you could also try the last beta, v17.3:

Also, a clean flash of your roms stock boot.img would be a good Idea before trying each.

https://github.com/topjohnwu/Magisk/releases
[Magisk] FuSan:
Seems like lot of users facing the magisk doesn't request root permission problem now. I am for that also. But for me it doesn't request root authentication when its not running in background. If I go to the app that requires root and open magisk root authentication comes up. Or open magisk than immediately opening the app also works. But root authentication doesn't come up unless the process is in background.

Edit: I am on redmi note 5/pro (whyred) latest xiaomi.eu beta.
[Magisk] Vishal P:
Google Pay is not working after updating to Magisk 18.0. Anyone else facing this??
[Magisk] martyfender:
Have you tried removing Magisk Manager from battery optimization in Android settings, then rebooting?