yashsingh1/xdaforums huggingface dataset:
[Magisk] Captain_Throwback:
I already said to wait for v7, but it seems you want a different response, so....:rolleyes:
[Magisk] knipp21:
Search for the app automagisk. It might do what you want
[Magisk] EViollet:
Send the following command to unroot :

$(getprop magisk.supath)/su -c "setprop magisk.root 0"

And to root again :

$(getprop magisk.supath)/su -c "setprop magisk.root 1"

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[Magisk] grep_i:
It's an Asus device isn't it ?

In OP he states that Asus devices need some work on the boot image and you need to contact [MENTION=4470081]topjohnwu[/MENTION] to give him details so he can fix that issue.
[Magisk] Captain_Throwback:
Where does it say it will probably be working in v7? It says a developer needs to provide the necessary information for him to start looking at it. I doubt there will be support in v7.
[Magisk] grep_i:
My bad when I saw my mistake I changed it but you already had my post in your buffer.
[Magisk] hoangbk56:
hi

have worked in Sony device??
[Magisk] Rayman96:
Look at my post in this thread regarding Lenovo A7-30. If you can do the same, then somebody can help. You are just moaning for nothing.

---------- Post added at 15:56 ---------- Previous post was at 15:55 ----------

What is your device? Can you run same commands as I did in my post about lenovo A7-30 in this thread?
[Magisk] Secundus:
can not uninstall magisk

i have flashed all files. Magisk does not work on my Samsung Galaxy S4 I9506 . if i turn Root toggle off it goes on one second later. And Hide selinunx is grayed.

Now i want to boot in to Recovery to flash the uninstall but it does not work. no recovery on my Samsung!!

I have read i must flash the boot.img to remove magisk. i have a backup in twrp. i have tried twrp manager but it needs root. i don't have root. reflash of twrp does not help.

please can anyone tell me how do i remove magisk completely?
[Magisk] Omel:
Sorry for my noob question have anyone any luck install. Viper4android on a note 4 or note edge and have it working

I could sure use some guidelines
[Magisk] SB13X:
Yeah I have it working on a Z3

---------- Post added at 04:16 PM ---------- Previous post was at 04:14 PM ----------

Update coming through for Android Pay is it still working? Can't test myself right now?
[Magisk] boilavera1980:
Are you on CM? Then you need to unroot first.
[Magisk] ibrokemypie:
is magisk still working to get around safety net? flashed rom update which wipes /system before installing,. then installed magisk and phh root, only other things i have flashed have been magisk modules, but even afterunmounting safetynet is tripped.

is there any way to check what tripped it? the rom dev spent a few days getting magisk working so i dont believe the rom is the problem...
[Magisk] Captain_Throwback:
Yes, it's working fine, as long as you don't have Xposed installed or enabled.
[Magisk] lebeneur:
I booted on my stock rom, with stock 6.0 boot img.

I go in TWRP

I Flashed magisk6.0 (no error)

I flashed supersu 2.46magisk (no error)

I flashed aligator cbump (supposed fixing and signing boot).

Reboot...

boot stuck with this message ...fastboot mode enable

Does ianyone succeded in installing magisk on a LGG3 ?
[Magisk] GXGOW:
If you don't use Xposed, it's working flawlessly. Otherwise, you'll have to disable Xposed, reboot and re-enable it once you're done using the application which uses SafetyNet. That's what I'm doing and yes, it sounds like a band-aid kind of solution, but hey, it's working for now.
[Magisk] ibrokemypie:
systemless xposed doesnt work?
[Magisk] toshi127k:
The way to the destination has been shown #3302

I can not show procedure that all users can understand,sorry

**********************************************

this is for

Xperia Z1compact(D5503)

Stock ROM 14.6.A.1.236

only

download boot.img on your PC

download Magisk-v6k.zip on your device

Please perform the following steps in place flash Magisk-V6.zip

reboot device into bootloader & flash boot.img

fastboot flash boot boot.img

reboot device into TWRP & install Magisk-V6k.zip

All please go at your own risk

**********************************************

please do not ask me any more
[Magisk] robert2103:
No work in kk . El manager magisk

enviado desde algún lugar del mundo
[Magisk] matif525:
I can't use a app to add other app to system app folder in my S-ON M7, but it's available to change system host file in Magisk mod by AdAway,

is there anyone tell me how to add apps to system?

Or it's impossible?

Thanks in advanced.
[Magisk] go vegan:
Are there any system settings that might resolve this? Or is it just a limitation of Marshmallow?

Would it be a reasonable feature request for an option (eg a checkbox option) to revert back to the old behaviour?

I'm assuming this is because I'm running an older version of Android on this box, and I'm assuming I'm not the only one using Magisk with older devices.

Alternatively, should I just use an older version of the Magisk Manager? If that's the best solution, what version should I roll back to? What's the best way to roll back? What problems might that invite?

FWIW, the U9-H is a damn good TV box, and I've got no immediate plans to upgrade. There was a Nougat update for it, but it caused more problems than it solved, so 6.0.1 is essentially the final update for it. But like I said, it's still a box I'm very happy with.

* Edit - Looks like there's (at least two different) 3rd party Android 7.1.2 updates available, but (1) not sure if this will fix the Magisk problem and (2) not sure if I want to deal with a 3rd party update when everything else on the box is working well.
[Magisk] martyfender:
Would changing mm settings to always grant, help? I don't quite understand your problem
[Magisk] palmbeach05:
If i were him, i would check on the referenced broadcast blocking first. If it is blocking, then there isn't much he can do
[Magisk] linkhyrule5:
So, I've been having some grief trying to get Magisk installed on my phone.

Running Android 9 on a Pixel 3 XL. No custom anything when I started, except for an unlocked bootloader. No root.

First thing I tried was what I thought was the standard install instructions: install TWRP, install Magisk. Rebooted, got stuck on the big G loading screen for a few minutes before it rebooted itself into recovery.

Then I read ahead a little more about installing TWRP being a bad idea on A/B devices, so I flashed in the factory boot.img, fastboot-booted directly into TWRP without installing it, and tried to install Magisk that way. Bootloop.

Then I tried downloading the Magisk Manager, patching the boot.img, and then manually flashing it into boot_a and boot_b both myself. Bootloop again.

So, that's me out of ideas. What do I do next? I'm guessing the thread'll want logs but I have no idea what a logcat is or how to get one from my startup. Right now this phone is also my only internet connection, so I'll need detailed instructions before I reboot it again if that's what we're going to do.
[Magisk] sdamark:
Should check out [MENTION=4810220]Homeboy76[/MENTION] guide. It's very concise, thorough, and easy to follow. He'll get you going again.

https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
[Magisk] go vegan:
How would I check that?

And again... Would it be feasible to install an older version of Magisk Manager? Would it be reasonable to request an option in Magisk Manager to emulate the older behaviour which didn't cause this problem? Would upgrading to Android to 7.1.2 solve the problem?
[Magisk] Tabish0099:
did you tried downloading Magisj flashable zip? type in the gogle "Magisk Flashable Zip" without quotes and download latest Magisk 19.3 zip from magisk web and then simply flash the zip file with twrp and no worry that twrp is asking for password this is because without entering the password you will not be able to decrypt data partition
[Magisk] zgfg:
Btw, Magisk has no Web site, except for directly from Github

But there is XDA thread reserved for Magisk, MM, Uninstaller releases, see OP post #1 for downloads:

https://xdaforums.com/showpost.php?p=68966662&postcount=1
[Magisk] Didgeridoohan:
Don't do that... You'll only find a whole bunch of sites that have nothing to do with official Magisk. In best case they're just trying to make ad-revenues, in worst case you'll end up installing something shady to your device.

Only ever download from [MENTION=4470081]topjohnwu[/MENTION]'s Github...
[Magisk] shoey63:
Some slot a/b devices need dm-verity disabled in vbmeta partition. Magisk doesn't do this.

So extract vbmeta.img from the update package and use the following fastboot command.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Then try rooting with Magisk by zip or modified boot image.
[Magisk] ilarson007:
This worked for me, thanks.
[Magisk] bunklung:
Android 10

Has anyone taken the Android 10 OTA for their Pixel 3/XL? I am curious if works. It just dropped a few hours ago.

*edit* decryption not working in TWRP

https://xdaforums.com/showpost.php?p=80177207&postcount=1168

Can we still sideload the canary version in TWRP?
[Magisk] Artim_96:
Using canary, yes.

And no, without working TWRP you can't just sideload canary through TWRP. So you either have Magisk installed, get the canary manager and let it update Magisk or you get the canary manager plus the firmware image from Google, extract boot.img, let manager patch it with latest canary and flash it through fastboot
[Magisk] eelik:
MagiskHide detected by RootBeer Sample

Hi, I have been struggling to get LastPass working on my rooted device for a few days now. I read a few replies on this thread dismissing as just warnings, but I think I found where it becomes an issue: when you use a corporate account and your company ticked the "not on rooted devices" box (it's byod, I didn't root my company's phone). I tried quite a few steps from didgeridoohan's "Hiding root from apps" to no avail (chmod, disabling adb, etc).

I have a OnePlus 7 Pro with Android Q Developer Preview 4 for OnePlus 7 (downloaded from oneplus's forum, can't post url) and Magisk 19300.

After finding no success, I decided to dig a little deeper by looking for potential dependencies or messages in logcat. As it was my first time looking at logcat, it was a bit hard to separate signal from noise and didn't find much.

I downloaded ApkStudio and "reverse engineered" the LastPass APK. After some digging, I found that it uses RootBeer. I downloaded the library off github and looked at the code. I found some log messages, and looking back at my logcats, sure enough, I found this:

[ 09-02 09:38:13.675 5718: 5718 V/RootBeer ]
RootBeer: a() [11] - /sbin/su binary detected!

Looking at RootBeer documentation, I found that they have a sample application called "RootBeer Sample" available on Google Play. I installed it and added it to MagiskHide. No matter how hard I try, 3 tests fail:

SU BINARY, checks for "su" under various locations. I have "su" under "/sbin/".

SU EXISTS, checks "which su". It probably returns "/sbin/su"?

ROOT NATIVE, appears to be similar to checkForBinary(BINARY_SU), but through JNI

I indeed have an "su" binary under "/sbin/". Whether that is normal or not, I do not know. I read stories about people having "su"s floating around due to previous rooting attempt, but I just bought this phone. I don't know whether that "su" should not be there, or it's normal that it's there but should somehow be hidden by smoke and mirrors (aka MagiskHide).

Should I just remove "/sbin/su" or that would break the rooting entirely?I come from a linux background, and messing around with su sure doesn't sound like a good idea!
[Magisk] warrencoakley:
Just updated to Android 10. Tried flashing the latest Magisk Canary Module with TWRP and get "Invalid Argument" when you reboot it goes into a boot loop. I have to reflash the image to get out of the bootloop. I have the latest Magisk manager installed no problem but just getting errors when trying to flash the zip. I'm on a Pixel 2 XL. Any ideas on how to get this working please? See attached.
[Magisk] Tabish0099:
How did you flashed magisk 19.4. Latest magisk version is 19.3 its means you did not flashed official magisk try to download magisk 19.3 from github
[Magisk] Didgeridoohan:
Magisk v19.3 is the latest stable release. The v19.4 releases are Canary bleeding edge builds that are just as official.
[Magisk] Artim_96:
Well, I bet TWRP for the pixel 2 supports Q as little as it does on other pixel devices. So don't try to install it through TWRP, patch the boot.img and flash that through Fastboot
[Magisk] warrencoakley:
19.4 is the Canary build. I tried the stable and the result is the same.

---------- Post added at 08:15 AM ---------- Previous post was at 08:14 AM ----------

Also tried this and it goes into a bootloop too.

---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------

Also tried this and it goes into a bootloop too.
[Magisk] Artim_96:
Have you paid attention to "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" being enabled on Manager before patching?
[Magisk] warrencoakley:
Also tried this and it goes into a bootloop too.

---------- Post added at 08:19 AM ---------- Previous post was at 08:18 AM ----------

How are these enabled and disabled?

---------- Post added at 08:21 AM ---------- Previous post was at 08:19 AM ----------

How are these enabled and disabled?
[Magisk] Artim_96:
They both have to be enabled, otherwise they mostly lead to bootloops
[Magisk] warrencoakley:
How do enabled and disabled them in Magisk Manager?
[Magisk] warrencoakley:
Yes both are enabled as you can see.
[Magisk] warrencoakley:
Would it be because I'm flashing a Canary build instead of a stable? Hadn't had this issue before when updating security patches on pie. Use to always flash the latest Canary in TWRP.
[Magisk] Artim_96:
Nobody knows. The pixel 2 is a bit different from my 3a in the way of system-as-root and stuff. Of course you can still try the stable version. For all I know it should work with Q, it just had a very bad way of handling sar which was fixed in canary
[Magisk] warrencoakley:
As you can see I flashed the stable version no dice, the the 19.4 Canary build and the same. Even tried the unistaller as a last resort and it keeps coming back with the same result with the same error "invalid argument"
[Magisk] Artim_96:
Like I said, it can't work in TWRP since it's not compatible with Q
[Magisk] warrencoakley:
So how did you manage to flash it and get it working in Q?
[Magisk] kiwigi:
Backup

With the latest Magisk and stock recovery, which app do you use to make a full backup(nandroid)?

Thanks for any suggestions.:)
[Magisk] Artim_96:
No app can do that, wait for TWRP to become compatible

---------- Post added at 10:20 ---------- Previous post was at 10:17 ----------

Besides the fact that I installed Canary on pie before switching to Q beta, I had to reinstall it later and I just did through fastboot. Had to uninstall and reinstall Manager since it was thoroughly convinced Magisk was not installed. But like I said, it was on Pixel 3a. The Pixel devices might be similar but not identical
[Magisk] kiwigi:
Is that really going to happen??
[Magisk] Artim_96:
Besides the fact that I installed Canary on pie before switching to Q beta, I had to reinstall it later and I just did through fastboot. Had to uninstall and reinstall Manager since it was thoroughly convinced Magisk was not installed. But like I said, it was on Pixel 3a. The Pixel devices might be similar but not identical

---------- Post added at 10:21 ---------- Previous post was at 10:21 ----------

No, they will just suddenly stop developing stuff at all [emoji854]

---------- Post added at 10:23 ---------- Previous post was at 10:21 ----------

No, they will just suddenly stop developing stuff at all [emoji854]
[Magisk] warrencoakley:
I can't unistall Magisk Manager as it doesn't give me the option to do so. When I try to flash the unistaller it gives me the invalid argument error. When I try to redownload it it gives me a parsing issue. See attached.
[Magisk] Artim_96:
No, they will just suddenly stop developing stuff at all [emoji854]

---------- Post added at 10:43 ---------- Previous post was at 10:33 ----------

The app, not Magisk. And if you don't even know how to uninstall an app you should Didi of all visit an how to Android 101.

And for the last time it makes no sense to even boot to TWRP when it's not compatible with Q

---------- Post added at 10:44 ---------- Previous post was at 10:43 ----------

The app, not Magisk. And if you don't even know how to uninstall an app you should Didi of all visit an how to Android 101.

And for the last time it makes no sense to even boot to TWRP when it's not compatible with Q
[Magisk] warrencoakley:
I know how to unistall apps I don't need an Android 101. I explained in my posts how I cannot unistall it. Thanks for the smart comments and zero help.
[Magisk] Artim_96:
... Did you make a system app of it? Otherwise there is no way that it can disallow its uninstall
[Magisk] warrencoakley:
Has anyone managed to get Magisk working on stock Android 10 (not betas) with a Pixel 2 XL without getting errors?

---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------

Hi. I'm trying to do this command but I can't seem to get it to work. Can you help incase I'm doing something wrong please?

---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------

Hi. I'm trying to do this command but I can't seem to get it to work. Can you help incase I'm doing something wrong please?
[Magisk] palmbeach05:
Flash twrp

---------- Post added at 12:38 PM ---------- Previous post was at 12:01 PM ----------

Android 10 just got released yesterday. Magisk has not been adjusted to work with android 10 as the source code also just got released yesterday with updates as needed. How do you expect that within 24 hrs of a new android version being released, that this process would be without error on the new android version? Cool your heels and be patient.

---------- Post added at 12:39 PM ---------- Previous post was at 12:38 PM ----------

Android 10 just got released yesterday. Magisk has not been adjusted to work with android 10 as the source code also just got released yesterday with updates as needed. How do you expect that within 24 hrs of a new android version being released, that this process would be without error on the new android version? Cool your heels and be patient.

---------- Post added at 12:45 PM ---------- Previous post was at 12:39 PM ----------

Android 10 just got released yesterday. Magisk has not been adjusted to work with android 10 as the source code also just got released yesterday with updates as needed. How do you expect that within 24 hrs of a new android version being released, that this process would be without error on the new android version? Cool your heels and be patient.
[Magisk] warrencoakley:
Heels are cooled. Since Magisk has been working on all Q beta's I would of thought it would be capable of running on the final release.
[Magisk] eelik:
I should have specified that I can pass SafetyNet check with success, both ctsProfile and basicIntegrity. Google Pay doesn't seem to complain, but I was unable to confirm that MagiskHide works beyond that. The first two applications (LastPass and Tangerine (my banking app)) I tried to hide detected the rooting. This is what led me to dig down LastPass a bit and find out about the RootBeer library and sample application. It seems that MagiskHide fails to hide root from RootBeer Sample on my phone. Is there a "standard" application that can be used to test rooting? Do people use RootBeer Sample as a way to check that hiding works? Does it work for anyone else?
[Magisk] jcmm11:
Root beer fresh, which has some additional tests.

https://play.google.com/store/apps/details?id=com.kimchangyoun.rootbeerFresh.sample

You should be able to get all green. For starters try Canary rather than stable. The only things I did to get all green was check Rootbeer in Magisk hide and also hid the Manager.
[Magisk] warrencoakley:
If you are on Android 10 I found this to work to install Magisk. But be warned, some modules would not be updated so if you install them that are modules that are not in the repo you can go into a bootloop.

https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
[Magisk] Ch3vr0n:
i followed the OTA procedure but after the reboot magisk was NOT installed. Tried the patched boot method, didn't work either (even tried flashing it to boot_a and boot_b, ended up in a bootloop. Flashed factory image (removed the -w) to get back up and running. Tried flashing through TWRP 3.3.1-2, didn't work either. Didn't prompt to decrypt data.

now from what i read in the posts above magisk code isn't yet updated? Yeah, knew i should have waited. Was the first OTA i received after unlocking and rooting my PIXEL 3 XL and wanted to try the procedure. Guess i was a bit too early, ah well. At least magisk isn't the only thing that will need an update :p (hint twrp)
[Magisk] warrencoakley:
It does work. See my post above.
[Magisk] Strephon Alkhalikoi:
Oddly, both TWRP and Magisk work properly here on my P2XL running Android 10 final. I didn't have to do anything special to get it working either, though I did have to remove all my modules as they haven't been updated yet for Android 10. I wonder if Magisk working may be due to my taking the OTA rather than clean flashing.
[Magisk] Ch3vr0n:
I tried the guide above (using 'canary' chznnel' didn't work for me. I'll just wait
[Magisk] kiwigi:
Thanks

Is that not a conflict as I could not use TWRP ( according install manual) during install of the latest Magisk?:confused:
[Magisk] Master K:
I am also running a Pixel 2XL and it is my standard procedure to use the OTA file in TWRP. Is that what you did that worked for you?

I normally flash the OTA, reboot and then go back into TWRP and flash the Magisk zip. Is that what you did or did you use a different procedure?

Thanks.
[Magisk] bbarnes1:
I installed a fresh factory image on my og pixel, sailfish

I can install magisk, but i can't mount system as RW

sailfish:/ # mount -o remount,rw /system

'/dev/block/sda33' is read-only
[Magisk] jcmm11:
And that's the way it's going to stay

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post80182839
[Magisk] Strephon Alkhalikoi:
Yep. You got it. :)
[Magisk] Gunner0X:
How to install Magisk for Asus Zenfone Max Shot - ZB634KL

I wonder if there is anyone who can help me to root Zenfone Max Shot, this device was initially launched here in Brazil, but so far I don't see anything here on XDA talking about how to root this device, not even custom roms.

Can someone help me? :)
[Magisk] warrencoakley:
How did you remove your modules? For me i see this but can't access them?

PS never mind. I used the file explorer in TWRP.
[Magisk] Artim_96:
Well, you need to either be able to install/boot TWRP or you have to be able to get your hands on the boot.img for your device and flash it through fastboot.

If neither is possible you are probably out of luck and you'll have to wait for someone to make one of the methods possible. Or to be able to create a prerooted firmware that you can flash
[Magisk] zerokarizmuh:
Magisk Canary working on Android 10, .20 build, on Pixel 3 XL

Ch3vr0n, I can confirm this works.

Under 'Advance Settings', make sure both options 'Preserve force encryption' and 'Preserve AVB 2.0/dm-verity' are selected before patching. I didn't have 'Preserve AVB' selected on my first attempt, and it failed. However, once I enabled AVB, then re-patched the boot image, it worked. Hope that helps. Cheers!