yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
a) AFAIK, the only possible way now (supposing you have EMUI 9 or 8 with Security patch 2018 Jul or later) is by opening the phone and flashing via TestPoints method, check in this Telegram group: https://t.me/joinchat/MtyvC0TmAuRnwZ0cimIEag

Their service will cost you cca 30 EU by PayPal

b) If older firmwares exist for your Huawei device, you can rollback (again via Testpoints, on your own) and buy the BL code for usual 4 EU

In case (but not in case [a]) you will need to flash from Linux, you can use Virtual machine on Windows to boot to Linux
[Magisk] Vvh:
Hey all, just did a clean update to Android 10 on an original Google Pixel, and I can't get past the Google Logo after flashing the patched boot.img using the latest (as of this writing) build of Canary.

Any advice? If I flash the original img, phone boots up just perfectly.
[Magisk] Apo11on:
Anyone?...Is there a boot/system setting, or Magisk setting that can be manually tweaked by modifying Magisk config files (not through UI) which would prevent the phone from rebooting into non rooted OS without Magisk?
[Magisk] Tulsadiver:
Did you uninstall magisk-modules first?

Boot this image. Remove the .zip as it wasn't zipped up, just renamed. You'll boot rooted magisk core-only. Uninstall magisk, then reboot. You may have to install Android 10 again.

https://www.androidfilehost.com/?fid=1899786940962604189

fastboot boot image-newpixel.img
[Magisk] Vvh:
You're epic, thank you so much for the help. The image you provided worked perfectly as a rescue image so I could uninstall all my magisk stuff. I believe the problem was EdXposed Sandhook version, as everything had been working fine before installing that module. Thank you again, seriously, kept me from another fresh wipe.
[Magisk] Tulsadiver:
I'm glad you got it back. Wiping is a huge pain.
[Magisk] Vvh:
Seriously. I had to wipe because Android 10 apparently corrupted my file system when I try to dirty flash it. Never had that happen before, so go figure.

Thanks again though. I had just gotten all my apps set up before I did the magisk patching, haha.
[Magisk] drezz2:
I have a doubt, having magisk, if I use lindk2d to make a system app, if the phone is reset, would it resist that application or be deleted?

for example I see that cerberus is copied to "/ system / priv-app" which is where it has to be but I see a mirror branch of it in /sbin/.magisk/mirror/system/priv-app that apparently contains the same and They don't seem to be a symlink, what is the meaning of that copy?
[Magisk] martyfender:
I use the Magisk module: App Systemizer (Terminal Emulator), to systemize apps, such as Greenify. Once installed and you reboot, you open a root terminal and type: systemize, to see the available options.
[Magisk] drezz2:
But it is not the same as using link2sd?

and the /sbin/.magisk/mirror/system/priv-app folder, what is your purpose? I think it contains the same as "/ system / priv-app", right?

I have never used modules in magisk, I had seen problems to uninstall or update having modules long ago (or something I thought I saw, although I do not remember the details of what happened)
[Magisk] paprykarz:
Hi, I'm using a OnePlus 6T with latest OOS and Magisk 19.3 and have a problem with in app payments. They just never seem to work and I always get an unknown error. I've tried using Magisk Hide on the app itself, Google Play and its services, but to na avail. Magisk Manager says that I pass the Safety Net and I can use Google Pay with no problem. Is there some step that I'm missing which allows me to pay for in app purchases?

Thanks in advance
[Magisk] ktmom:
Link2SD is doing a similar thing to App Systemizer but as far as I know, does not make apps, system apps. In this way they are used for different functions.

From the Link2SD description:

Doing systemless modifications means not writing to or even mounting the system partition. This is the point of App Systemizer. It is a module that "systemlessly" makes non-system apps, appear to the OS as though they are system apps.

You mention the app showing up in the /sbin/.magisk/mirror/system/priv-app directory. That is the real directory being used. It is bind mounted during boot so it appears to be on the system partition. This is sometimes referred to as a system mask. You can read more about how Magisk does it's thing on the Magisk Details page.
[Magisk] drezz2:
I thought this was going to be easier for me to understand: /

eg in the cerberus manuals it was always indicated to use link2d to turn it into a system app and as it really appears in / system / priv-app because I thought everything was correct

unaware of the existence of /sbin/.magisk/mirror/system/priv-app folder

then before a reset I will be losing the converted applications?
[Magisk] PoochyX:
Link2sd is a good app it's hard to master tho

([emoji3590]09-09-18[emoji3590])
[Magisk] OfficialJohnGL4:
I found a new option in Magisk Canary, what does "Recovery Mode" stand for? Magisk for Recovery Mode?

Edit: I found its for patching recovery image. Bummer, but its kind of a cool feature tho.
[Magisk] PoochyX:
Why use canary it's bleeding edge

([emoji3590]09-09-18[emoji3590])
[Magisk] palmbeach05:
Not to go too ot, but 19.5 has better sar compatibility, specifically in regards to a only devices (feature not implemented in 19.4 (beta branch), a/b devices only) (sar compatibiluty not seen in 19.3 (stable branch)), additional support for legacy qcom and exynos devices, and a few other things along the way.

As a a only, non sar device user, to me it doesn't matter which one i use. But everyone is different.
[Magisk] ktmom:
I don't use or know much about Link2SD and this isn't a support thread for that app. Whether you loose the app after a factory reset really depends on whether the app is actually a system app or bind mounted or symbolically linked.

As far as using Magisk to make an app a system app, if you don't wipe the user data (keeping installed modules) and install Magisk back if lost during an update, then the app should continue to be a system app.

If you have used a process (maybe link2SD) to actually mount the system partition and then move an app to the system partition, changing it's permissions along the way, then unless the system partition is wiped, that app will stay a system app.

I don't think you have mentioned your device. How individual devices work is different. A 2014 device is very different than one released with Pie in 2019.

If you boot to recovery and use either a file browser in recovery or ADB, look if the app is in the system partition. If you see it when booted to recovery, then it has been installed there. However, if it's not there when in recovery, but is when booted into the OS, it's either sym-linked or handled through Magisk's system mask.

As far as link2SD goes, just because Magisk does it's thing without ever writing to the system partition, doesn't stop other apps from using root access to mount then write to the system partition.
[Magisk] martyfender:
I use a similar app, Apps2sd and it has a similar function to move apps to system. If I am not mistaken, this is done in both apps by modifying the actual system, not done systemlessly, like the module I mentioned. You are really better off doing it systemlessly, as far as I can tell. Android 10 devices will not even let you modify the system, as far as I can tell, by what has been written on several threads. I think in the long run, even if you are not yet on 10, that you should do it systemlessly.
[Magisk] weysonn:
Does anyone know if Magisk can hide Google for Work on Android 10? My work was able to detect that I was rooted and had me remove Magisk. Wondering if I set it up incorrectly or if theres anything I need to hide in Magisk. Thanks in advance!
[Magisk] martyfender:
Canary has quite a few fixes for many devices, so I believe that many users can benefit from it, if they read the changelog and see that it could potentially benefit their devices. But you are right, in the sense that there could possibly be bug in such a cutting edge version.

I personally have 4 of the same devices and I use these bleeding edge builds on all of them, with very few problems. I am, however a tester and as such, I expect to find bugs and report them to [MENTION=4470081]topjohnwu[/MENTION] on github, when I find them, if I think it is significant to report.

I do, however, have a good backup plan and can restore if I have a fatal disaster.

They are all tablets, so they are not as crucial as a phone. I have an Iphone for that critical function. I just need tablets for the screen size. I would not want to view these forums and telegram on the small screen, on breaks at my job on the Iphone.

---------- Post added at 10:39 PM ---------- Previous post was at 10:19 PM ----------

Did you hide the Magisk Manager in settings, then delete your apps data and cache and launch them again to see if it still detects root?

You are the first person I have seen to mention Google for Work. There is a special module and technique for Microsoft business apps, intune, etc. Maybe this will require similar, unorthodox methods as well. Is this the link to what you are talking about?

Since many, many, other apps have ways to detect root, despite all of topjohnwu's attempts to circumvent it, I would think Google would easily be able to do this as well.

https://gsuite.google.com/
[Magisk] lollazzo:
There is a problem with magisk on my s5 with tw rom:

If I search a module in the download tab it crash. The same thing happen If i try to add a module in the module tab. I tried to flash module with twrp but update error 1 occurred.
[Magisk] RandomPooka:
Have you tried wiping the app cache or data for the manager app?
[Magisk] rohankmr414:
Magisk hide isn't working on my redmi note 4... It is running pixel experience rom
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHideIssues
[Magisk] YandereSan:
Having a bit of a problem.

Magisk v19.4, and I have verified that MagiskHide works properly with Terminal Emulator.

I am trying to use this application: https://www.apkmonk.com/app/jp.eplus.android.all.app/

But it utilizes some kind of obnoxious module called FxShield which is detecting root via the /sbin/su binary.

Seems to be completely bypassing MagiskHide.
[Magisk] Ch3vr0n:
Ever since updating my pixel 3 xl to Android 10 I've been using canary magisk(and manager) to root. I see that v20 stable has been released. What's the simplest way to go back to the normal manager and stable update channel? Flash stock boot? Sideloading v20 zip via twrp boot? Magisk uninstaller?...

Now that there's native A10 support I'd like to 'go back'. I am NOT using ANY modules other that magisk's own systemless hosts.
[Magisk] zgfg:
Just change Channel in MM Settings to Stable, and (maybe not needed) restart MM

Then update MM and M

By changing to Stable MM you will loose options to choose Canary channel.

So you can also stay on Canary and update to the latest/corresponding Canary v20. 1

EDIT: And confirming Canari MM b244 and M b20001 working fine on Huawei P9, EMUI 8
[Magisk] hfam:
Heya zgfg,

Interesting. I just updated to stable 20 today from Canary 19.4 and you're right, when I choose my custom link which pointed to Canary channel, MM just sits checking for update. It used to reflect the current Canary release for M and MM.

Is there a new link to Canary channel to use in the custom link? If not, how does one get back to Canary channel if desired?

Thanks, and for the record the latest stable v20 works perf on Pixel 2, Q, Oct sec update
[Magisk] fash_ahmed:
Issue with Magisk Manager 7.3.5

Everytime I enter settings, the app crashes.

Everything else... Modules, download, hide etc... Is working fine.
[Magisk] wawanRedblack:
After update magisk 20

I can't access stock recovery mode

It says "Qualcomm crashdump

Attempt to kill init"

I'm on Oneplus 7 pro OOS 10 Beta 3

And how to get back to 19.4 version?

Btw, i don't have custom recovery

Thanks
[Magisk] samep:
Same here. Crashes shortly after opening MM settings but all else appears ok.

I've cleared MM data and reinstalled and results are unchanged.

Edit: I updated to MM 7 3.5 and Magisk 20 stable just released today. Stock Android 10 on Essential PH-1
[Magisk] PoochyX:
Is that on the new canary Verison

([emoji3590]09-09-18[emoji3590])
[Magisk] Looki75:
Same for me
[Magisk] demonoidmaster:
My rom did use system as root a while back but that didn't last long as it was just dropped and went back to good old /system way of doing things

So uhh, magisk is made for system as root only now? I'm not risking bricking my device if a weird massive change has been made like this
[Magisk] jcmm11:
System as root only? No, what gave you that idea. That would mean no support for lots of systems
[Magisk] PoochyX:
The whole concept of Magisk is Systemless this guy just gave me flashbacks to supersu with this post [emoji817]

([emoji3590]09-09-18[emoji3590])
[Magisk] XtraWater:
after update to V2.0 my phone booted into fastboot. Mi A1 RR6.2
[Magisk] mauro_cbc:
After update to v20.0, Magisk crashes, it don't install properly and modules don't work, they even not apear on menu...

O tryed to flash update from recovery (TWRP), but no success... Same issue...
[Magisk] demonoidmaster:
Yeah well magisk switching from /system to /system/system is a big difference and I'm not willing to risk it

Unrelated example but still an example of **** that could go wrong: Earlier today i updated my rom, yknow what that did? Boot up to the Mi logo then device shuts down refusing to boot, when plugged into a power source it would bootloop at the mi logo

Yknow what fixed it? Reflashing my recovery (twrp) which then worked, I've tested the scenario twice and both times were the same (got it to boot then rebooted to twrp and reflashed the rom zip again and rebooted, nada, only reflashing twrp fixes it), updating my rom (mokee 20191011 for Mi 6X) caused my phone to be a ****ing brick, thankfully i know about fastboot commands

But it's still weird, how can a simple rom update do this? My guess is it touched a file somewhere it shouldn't have, i might go back from the 9.9.3 beta xiaomi firmware to 10.3.6 even though it's quite old by now but it's worth a shot testing with it
[Magisk] PoochyX:
What magisk version are you using

([emoji3590]09-09-18[emoji3590])
[Magisk] martyfender:
You can update to today's Canary release, 20001.

Changelog: Sync with public release.

Or change your update channel back to the stable channel and update.
[Magisk] PoochyX:
Marty when is magisk 19.4 going to come out of beta

([emoji3590]09-09-18[emoji3590])
[Magisk] martyfender:
Is what on Canary, the same commits as the stable release?

Changelog:

---------- Post added at 08:49 PM ---------- Previous post was at 08:43 PM ----------

It already is: Stable Magisk Version: v20.0
[Magisk] Pbsipher1:
Hey everyone so couple weekends ago I purchased a zZTE Axon M z999. It was released by att exclusively in 2017. Phones pretty cool with dual screen 4 GB ram and 64 gb internal . I have been doing a lot of searching and still yet to find root for this device. Alot of false hope because everything but one says to put device into fastboot. But has no fastboot. Any advice l? getting root on this device would b pretty sweet
[Magisk] yashau:
Latest version stops the cell radio working on my OnePlus 7 Pro. Went back to 19407 and it still works fine.
[Magisk] lekcin18:
just want to report but just a minor problem.

i just updated latest magisk 20 and mm 7.3.5

i download a module and installed it but decided to reboot later then I look in my modules list, the recently module that I downloaded isn't there. only shows up when I rebooted my phone.

it wasn't like that before but just minor problem though
[Magisk] martyfender:
To check if it actually does not have fastboot mode:

Connect a PC with the proper drivers to the device booted into normal Android. From the PC command prompt or terminal, if using Linux, issue:

adb devices

hit the enter key, you should see the device serial number if it is connected.

If it is connected, issue this command:

adb reboot bootloader

hit enter, if it has a bootloader/fastboot mode it should reboot to that mode.

Unfortunately, if you get a completely black screen at this point, the manufacturer

may have

disabled bootloader mode. I have a cheap, Smartab tablet like this. Or there is some other way to do this that I am not aware of .

I found this for what appears to be your device:

https://www.androidweblog.com/zte-axon-m-z999-root-install-twrp-recovery/
[Magisk] Vuska:
Hi... Right I'm still in magisk 19.3 release.

Magisk already told me to update to v20.

but i dont want update to v20 now... because my phone S10+ G9750 still need v19.3

When v20 already out.... how do i Patch AP file with still v19.3 ?

i think if i patch bootimage from magisk manager.. it will patch the AP Tar file with latest magisk v20 not v19.3

Please enlighten ...

Thank you
[Magisk] martyfender:
After you install a module, you usually have to reboot for it to show that it is enabled.
[Magisk] Pbsipher1:
Yes it shows but when I reboot bootloader all it does is just restart phone that's it and I can type it over and over and still just restarts. I have viewed that post as well. I downloaded all files needed and just get errors and install fails. This phones has A LOT of potential if it can b rooted.

Oh I'm sorry no I did not c that but it's not correct at least for the model released in the us
[Magisk] PoochyX:
That was a typo

([emoji3590]09-09-18[emoji3590])
[Magisk] martyfender:
Yes, you should be able to patch the stock boot.img with Magisk Manager, if you have a copy of it on your device and tell MM the path to it.

Someone with a Samsung device please clarify if I have this wrong and if the .tar file needs to be extracted first to patch it.
[Magisk] TheXclusive814:
Updating from 19.4 to 20. Updated Magisk Manger and then tried to update Magisk, choose Direct Install (Recommended) and then I get the attached error

Pixel 3xl Android 10
[Magisk] guest4711:
Use https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json
[Magisk] Vuska:
how to set the path to MM ?

i try with /sdcard/download/ to custom source channel

MM cant find my magisk 19.3.... zip file already there..

Mmmm... i think a missunderstanding here...

what i mean is.. how to patch boot image with magisk v19.3 instead recent v20...

because when i patch now from MM, it will patch with latest one.. v20...
[Magisk] BillGoss:
Same thing happening here. Logs attached.

I'm using Magisk 20
[Magisk] martyfender:
I am speaking of patching a stock boot.img in Magisk Manager here, not setting up channels to flash Magisk through the direct install method, or download for twrp method. I would suggest you read the Magisk install documentation if you don't understand this.

I you already have a Magisk.zip downloaded, you can flash it from the module tab of Magisk Manager by clicking the + button, navigating to where the Magisk.zip is and selecting it to flash. The result is similar to the direct install, but with the zip you selected, instead of being downloaded and installed from the update channel. You will then be asked to reboot.
[Magisk] Vuska:
yup.. i just realize that sir...

but what i mean is... how to patch boot image with magisk 19.3 instead with v20.

because today if i patch boot image it will patch with v20 right ? not v19.3

v20 made my s10+ get a random reboot

and i dont use twrp /custom recovery
[Magisk] martyfender:
Read the rest of what I posted (UPDATED) above to flash 19.3.zip in the modules tab.
[Magisk] Vuska:
ok... get it...

will try this way.. :)
[Magisk] demonoidmaster:
Just back up your current boot img if it's already got patched by magisk
[Magisk] martyfender:
I believe you must still have root for the above to work, though. Sorry, I frequently go back and edit and update my posts with relevant information. Let us all know if that works for you.
[Magisk] torjohron:
Magisk is crashing when i enter "settings" now (I'm on beta) - any ideas?
[Magisk] PoochyX:
Which version

([emoji3590]09-09-18[emoji3590])
[Magisk] martyfender:
https://github.com/topjohnwu/Magisk/issues/1915

There is a Magisk Manager test apk linked there. You could test it and report there if it also works for you, which may help John.
[Magisk] torjohron:
Yepp, found tested and worked - have updated the github case :)
[Magisk] hfam:
Thank you sir! Have a fantastic weekend!
[Magisk] zgfg:
I think, custom links for Canary did change recently, but I don't use them - search in this and in the XDA Canary thread to find, it was posted about

Otherwise, just install latest Canary MM from XDA Canary thread, its post #1, and you will again have Canary and Canary debug channels options in the MM Settings
[Magisk] VoidedKN0X:
What exactly does this mean?

[MagiskInit] [2SI] Support non A/B setup (Android 10)
[Magisk] redplate:
nvm
[Magisk] FaflaMcDafla:
Device: Oneplus 7 Pro

ROM: Stock OOS 10.0.1

Magisk version: 20.0

TWRP: No. Stock recovery.

Issue: Can't get into recovery. Qualcomm CrashDump appears with Attempt to kill init! Code 0x00000100.
[Magisk] wawanRedblack:
Same here , im on OOS 10 Beta 3
[Magisk] Natanji:
Device: Pixel 3

ROM: Stock, October 2019 Update

Magisk version: 20.0

TWRP: No. Stock recovery.

Issue: After flashing the patched boot image, device won't boot. It will show the G logo bootscreen with a loading bar below it for a few minutes, then the screen goes black and device reboots shortly after.

I updated via OTA, in case that's an issue? And I used the boot image from this here factory image: https://dl.google.com/dl/android/aosp/blueline-qp1a.191005.007-factory-c36610c6.zip
[Magisk] XtraWater:
Hi.

Do you mean, after flashing Magisk restore the previous boot.img and all is good? Because my phone boots into fastbooot after latest stable update. Then I restored the whole backup.
[Magisk] redplate:
My G9750 HK works with 19.3 only.

20.0-20.1 = no root, no recovery, no boot at all. only stuck in kind of semi download mode.

19.5 = root, but random reboot fix isn't working.

19.3 = everything works

And to my question about patching 19.3 via Manager. Ofc I need successfully flashed magisk. Fortunately I had a 19.5 AP to acquire root, then flash back to 19.3 with zip via Manager.
[Magisk] Natanji:
After reading more in this thread, I now believe that this problem is due to bad modules being installed in magisk, causing the bootloop. I didn't know this could happen, and there was no warning of that prior :/ But how can I remove these modules now? TWRP doesn't exist yet for Android 10 so that won't work. Is it possible to get magisk manager to enable/disable modules even while magisk isn't installed? Is there some settings file that I can modify, or a place where the magisk image resides that I can reset from within stock Android? Because I can restore the stock boot image and boot all fine into my system, but well that doesn't help. Some people are talking about core-only magisk, how can I enable that? Or did someone like [MENTION=5346465]Tulsadiver[/MENTION] build this for Pixel 3 and Magisk 20.0 yet?
[Magisk] fanaticgamer:
Bug Report:

Oneplus 7 GM1900

Android 9, Oxygen OS 9.5.8GM57BA

The latest Magisk 20 breaks TWRP recovery from sticking after reboot.

I've also tried to downgrade to my previous twrp recovery and magisk versions but I still have the same problem, after reboot, twrp recovery is gone.

steps:

1) fastboot boot twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img

2) flashed twrp installer

3) then flashed magisk 20 from twrp

4) reboot

5) reboot recovery (from extended power menu)

6) It still ends up in fastboot mode, twrp is gone

There is also another person which reported the same issue: https://t.me/twrp_Mauronofrio/2292
[Magisk] rfgamaral:
I'm having the same issue and reported it over at GitHub.