yashsingh1/xdaforums huggingface dataset:
[Magisk] AquilaDroid:
Thanks, but could you edit your post there to reflect what question you're replying to so there's no confusion? Also, could you elaborate on the "ADB shell then delete contents of /data/adb" since I'm struggling with the ADB shell commands? Thanks for the prompt response!
[Magisk] Seanie280672:
Could someone tell me please, if I factory reset my S8+ will I have to go through the root process again before booting my phone for the first time so to speak ?

The reason I ask is after I installed TWRP and rooted with Magisk, also had to flash some other files to decrypt the device etc, after the phone booted for the first time, I went through the normal setup process then recovered a backup of all my apps etc, since then its been running like crap and ive read that I should of just manually installed everything again from playstore, so im thinking of living with it until about Feb or March when i'll get a new device or just factory resetting again and doing things properly this time.
[Magisk] Bielecki:
Guys, I successfully beat up McDonalds.

I updated to latest versions of McDonald's app, Magisk and Magisk Manager (not sure if necessary), repacked Magisk Manager (Settings -> Repack) with name "Manager" (you can choose whatever you want I think, I haven't tested if detects "root" or "magisk" words tho), unchecked and checked again McDonald's app in Magisk Hide, then cleared all McDonald's app data (not sure if necessary again) and voilà - McDonald's works like charm again.

McDonald's v2.4.1

Magisk v20.2-11b7076a (20109)

Magisk Manager v7.4.1-291c718b (262) (6)

Android 9 PKQ1.180904.001 (with kernel 4.4.53-perf+)
[Magisk] casouzaj:
My McDonald's app is v2.19.1. It runs fine in my Sony Z5 Compact phone, running a stock based custom ROM. It is in Magisk hide list and Magisk Manager itself is hidden (repackaged). Nevertheless, I use the stable Magisk v20.0, because with any newer versions, Safetynet tests fail.
[Magisk] RandomPooka:
Ahh, the popular McDonald's hack must have them tightening up security..LOL
[Magisk] XtraWater:
What's the proper way to figure out why updating from 19.3. To 20.1 ends in an bootloop? Is someone willing me to help?
[Magisk] Causical:
Never derping mind
[Magisk] DroidJP:
I just find this hilarious for an app such as McDonald's [emoji28]
[Magisk] casouzaj:
My McDonald's app has just been updated to v2.19.2, and it keeps working!
[Magisk] Hirishiolo:
Do you have YAP working with Magisk v20.1? I can't manage to have it working...

thank you
[Magisk] dcarvil:
Have you tried removing all your modules first? 20.1 works fine for me, and I haven't seen any problem reports for it.
[Magisk] XtraWater:
There are some reports about it.

The bootloop happend already when install magisk 20.1 directly after flashing the rom. It messes up my boot.img. It's a xiaomi phone. On my galaxy s5 it works perfect. Also on an S7.
[Magisk] LeifAlbor:
Stuck in bootloops after flashing Magisk stable/beta/canary over the December patch on my Pixel 2 XL. Magisk manager happily patches the boot image and I can push it on fine using fastboot, but that's as far as I get.

Logcat here -> https://drive.google.com/open?id=1BN...2JDSLyDJG--j-l (xda isn't letting me attach files for some reason)

Where am I going wrong?
[Magisk] JamesKinds:
I'm currently using magisk 20.1 and running into the known issue where new apps are not being granted root access.

To fix this in the short term I would like to downgrade to magisk 20.0 (which I believe did not contain the bug)

.

Can someone please provide step by step instructions for downgrading magisk from 20.1 -> 20.0.

There is conflicting advice on the thread and I don't want to brick my device.

Thanks in advance
[Magisk] jcmm11:
You won't brick the device. Just flash 20.0 on top of what you have, you'll be fine. You could also install Canary instead
[Magisk] vMAC:
Need some help or advice if you could please.

I had Magisk installed on my Pixel 4XL (currently o Nov 2019 patch) with absolutely no problems. After learning about FingerFace module I decided to try to load EdXposed. I downloaded the Riru Core module in Magisk Manager, then downloaded the EdXposed module (yahfa) in Magisk Manager. Lastly I downloaded the apk for EdXposed and installed it. Then I rebooted my phone. When I went back into Magisk it told me that Magisk was not installed. I went into EdXposed and it stated it was not installed either. Thinking all I needed to do was reinstall Magisk I downloaded my Google Firmware, took the boot.img patched it with Magisk Manager and then fastboot flashed it back to my phone. Then came the bootloop. Here are the things I have done to try to fix it to now avail.

1) I reflashed the stock boot.img (phone boots fine)

2) Downloaded the image again, in case of corruption, and patched it and reflashed (bootloop again)

3) Ran logcat (attached)

4) Tried this command: adb wait-for-device shell magisk --remove-modules

- Phone restarted but would not boot

- Ran another logcat and still seen references to Magisk

5) Reflashed the stock boot.img and have use of my phone but no Magisk.

So if anyone can help me to stop the EdXposed modules, or all modules from loading, I would be appreciative. Also if anyone can tell me what I might have done wrong or the steps necessary to get Magisk and EdXposed working on a Pixel 4XL please let me know.
[Magisk] JamesKinds:
Can I simply flash canary over 20.1 (stable) or do I need to first remove magisk via magisk-remove and then install canary?
[Magisk] Chaos234:
Well, I don't want the stock boot.img back. That boot.img which is delivered by the IronRom is fine for me. But since the dev has written an announcment here I'll wait until his work is finished

and see then, if it's working fine :).
[Magisk] QWEnter:
Can't say anything about Titanium Backup as I never used it to delete system apps but deleted them manually using Root Explorer right from /system/app and /system/priv-app. After rebooting they never appeared again so in your case I think it will be the same.

The case with physically undeleted system apps looks really strange and don't think it caused by Magisk. Looks like Titanium Backup wasn't granted with root privilegies during app removing process (btw, check it in SuperUser/SuperSu log) or something like that. Will be able to check how it works in my phone's case only after this weekend.
[Magisk] Azuritko:
Thank you very much. Done. But it was not easy. I had problem to install XZDualRecovery without root so I tried to root and it was also problematic but when I figured it out all I continued by your steps and hurray Magisk is installed.

P.S. To flash root.img I have used FlashTool.
[Magisk] basicline:
Hi everyone, I have a smartphone model BQ E6, I have a problem when making the terminal with root Magisk v6 and the old versions. La idea is that applications can see that I am root only when I want (Case pokemon). I have installed the version Lollipop (downloaded from the web BQ) and the TWRP 3.0.2.0 (downloaded from their official website).

I enter the TWRP with butom + and the power button and enter the recovery (up here all perfect) I give Magisk install and tells me "unable to detect boot image ".

The truth is that they no longer do or I'm doing wrong, in theory the bootloader is unlocked.

If'm sure I'm not root and I have not installed because the XPose format the phone before installing and then had to put the imei openthe phone and entering Engineer mode.

Any help will be very well received.
[Magisk] Didgeridoohan:
I can confirm. Just did a test on my Nexus 6, stock ROM. Magisk v6 and phh magisk 17 installed. Seems like TB doesn't quite work with phh's superuser, at least not the current Magisk version.
[Magisk] MYRONJAY:
Can I update SU binary in SuperSU app? I root my CM13.0 using the SuperSU zip I got here.
[Magisk] ammar_maher:
can any one please he;p me to explain how to install magisk im on Aryamod S7 Edge ROM and LSS kernel 3.6

my mobile is samsung galaxy note 3 n9005
[Magisk] ibrokemypie:
reports of this in the htc 10 leedroid thread too, definitely confirmed
[Magisk] putridfoetus:
TB doesn't play well with Magisk when trying to uninstall system apps. This is most likely because Magisk mirrors the stock system partition. Take a look in /magisk/.core/mirror and see what's there. In the OP, there is a section which describes how you can hide system apps with a module. Uninstalling anything in /system directly defeats the whole purpose of Magisk to begin with, which is to preserve a completely unmodified system partition.
[Magisk] JudgeDread11:
There is a sample unbload module in the modules thread. It's easy to adjust it. Removing bloatware with tibu will modify your system partition.
[Magisk] Turbopuschel:
Thanks. I also wanted to uninstall the system apps to install another app as system app and there is not enough free space without uninstalling something else first. Now when I want to uninstall some system apps and add another, does that mean I have to first uninstall Magisk, make the modifications with another root method and then install Magisk again?

Edit:

Thanks, I will take a look at it.
[Magisk] Captain_Throwback:
It seems you've completely missed the beauty of Magisk.

Magisk allows you to do both of the things you want to do, without even touching the system partition. So size is no longer an issue. Please read the OP and try to understand what this mod actually does and how it works. And review the module template because that is what will allow you to accomplish what you're trying to do.
[Magisk] Turbopuschel:
I guess so, the only part about Magisk I understood was that it could toggle root for using certain apps. I will try to understand how I can achieve want I want using Magisk.

Edit: Then again, the way this is handled probably changes with v7 so I'll wait just a bit.
[Magisk] yung40oz84:
Will you be updating to the latest version of superSU 2.78SR1 to a magisk compatible version?
[Magisk] Captain_Throwback:
There won't be a need for this with the new version.
[Magisk] heslo.rb26:
Works on my HTC10 with LeeDroid, running Magisk with PhhSU... Not sure why it's not working on other peoples devices
[Magisk] yung40oz84:
sweetness! Thanks for the reply
[Magisk] cadkey:
I have Htc 10, LeeDrOiD R176, magisk and Titanium Backup.

All works perfect here.

So you have a problem mate.
[Magisk] rtorres01:
Guys, I need lot of help YOU.

I did the procedure in hum Note 4 with custom ROM to 5.1. It ran everything, but I have not access normal root.

What can I do?
[Magisk] oTeMpLo:
Did you install phh superuser apk from playstore too? I think you missing that... Last step.
[Magisk] wilsonhlacerda:
In all my previous experiences you can go from stable to canary without problems (cause it is a version upgrade). The way around is not possible (downgrade) without cleaning first.
[Magisk] Markeee:
Failed to install Help ?

Looking for some help here

Just installed this new Mokee Android 10 rom on my Pixel C Tablet and getting this Magisk not installed error after I install Latest Magisk Manager 7.4.0

Magisk installs flashes perfectly from with-in the latest Twrp 3.3.1-0 but then when i boot to android and install Magisk Manager-v7.4.0.apk get the below error magisk not installed then when I try and install it from within magisk the install fails

Ran the latest magisk uninstaller a few times but still not allowing me to install Magisk after i install Magisk Manager

Any suggestions ?
[Magisk] davek17:
98% working!!

I have an odd issue, tested across 4 devices now.

I install Magisk and also the remove verity/encryption zip by topjohn. All works fine apart from 2 things:

I can't change either ro.product.brand, ro.product.device in system/build.prop on Android 8/9 devices

I have litereally managed to customise anything I want including app removal, backgrounds, bootanimation replacement, loads of build.prop changes other than the above. So I know Verity is disabled etc. I can even put everything back with Verity disabled (I know where verity is on these devices) but all devices simply boot loop if I touch the above settings.

I have spent like 2 months on this now and really need some help. Is anyone else getting this and can anyone shed any light on it?

I am unsure if its a Magisk thing or simply you can no longer touch these settings any more due to they may be tied to the fingerprint or GMS certificiation in some way?

Any help is greatly appreciated!
[Magisk] martyfender:
I believe with recent versions of Magisk, that you must do the above changes systemlessly now, with magisk modules that you or others make.
[Magisk] davek17:
I see, so may I ask a follow up question as I have not had much experience of the modules, although olots using Magisk! With the Magisk modules, do these have persistency when Magisk is uninstalled?

The reason I ask is that I ultimately want to get the Boot relocked and SU and Magisk taken off the phone so its back to normal but with changes and DM-verity permanently removed.

Could you tell me which modules would help

Dave
[Magisk] davek17:
So I have an update. I just did a crash course on modules, and installed the Getprop module. tweaked the system.prop in that to change the ro.product.device and ro.product.brand and I get the exact same issue. The device kind of boots up, I get a pop up saying "Android is loading", then the device screen goes blank, ADB is still connected at this point. The device then auto reboots into Recovery. It will then never boot, only into Recovery.

I tried the module with just a ro prop that I know i can change in the byuild.prop and it worked fine.

This must be an issue to lots of people? Surely there are lots of people trying to spoof Pixel phones etc. I just want top rebrand a phone so the original model in the settings and about panels on the phone giuve users a better place for support for a packaged uyp phone/software product.
[Magisk] Jeric10:
Hang-up Fastboot

After I flash magisk zip in twrp and my Realme RMX1911 /Realme 5 hang-up in fastboot mode then when I turn It off and on It again It still the same it returning to fastboot mode also when I charge It what must I do?
[Magisk] estofjlw:
Google is working hard . . . to stop rooting . . . of any kind. See my post at https://xdaforums.com/showpost.php?p=81236777&postcount=84

It depends on what device you have - but a Pixel and most phones running Android 9 or 10 fall into the spider's trap

I have an HTC ONE M9 I built off-line rooted with Magisk and Manager that hidden and it works fine - but of course it has only Nougat

I have Moto G7 Power I KNOW will be a problem if I do not do everything off-line and fully hide things before turning mobile data back on - these new phones actually report changes to them before even being allowed a signal from the carrier - if the carrier has set it that way - and as the true super user - "ROOT" the carrier can send spoilage files of which the only way to get the device working again is to make it stock again.

Once your IMEI is identified . . . it sort of gets on a "watchlist"

The sad reality is The Digital Millennium Copyright Act https://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act allows this because Android is a name brand of Google

As I said in my other post - an application like Magisk is a gray area and is technically legal as a system-less application - but they *Google and the Carriers who care about this) do not see it that way

So anything that modifies anything considered a system file will trigger a Google Trap usually - as said else where you will need a Magisk module for any hope of success.
[Magisk] davek17:
Well I am doing this on MTK devices largely. I have been doing it for 10 years and everything up to Android 8.1 we have been able to get done. Fully tested, as long as we don't touch certain props and we rem ove DM-Verity then all is good.

Android 8.1 is posing 2 issues for us as above, same for v9.0 and thats it. We're currently trying another approach!! I have the source code for the Settings.apk and we're changing the "model" in there to the "Other text" and it seems to have worked. I think this is enough for what we need.

To be honest how any MTK device passes GMS certification, the amount of apps that are tracking you and passing data back to China is beyond me how Google allow that.
[Magisk] ktmom:
I see that you have moved on, but I wanted to touch on this question. No, systemless changes do not persist of either the module or manual is removed.
[Magisk] ssamurai:
hello

I have a serious issue, it started yesterday

I did an update to Magisk after that I installed skype for bussines app and I had to hide it from magisk to make it work,it worked for a while but then it started crashing,I went and remove it after I removed it data and reinstall it which changed nothing after a while I discovered that there are some others apps that started to crash (my bank app and the phone operator) I didn't check all the app I did the same thing clear their data and reinstall them no result, so I tried to search in the internet I found nothing about the issue, I went and uninstalled Magisk completly after the reboot I tested those apps they didn't crash and they work fine, I went and flashed Magisk again the same old version I had before updating it after the reboot the aps started crashing again, I went and installed an older version 19 did a test same issue I realy don't know what happened.

If i want those app to work I must not have Magisk knowing that I need root for many app that I use...

I have Xiaomi Redmi note 8

here are some screenshots of the errors
[Magisk] ssamurai:
forget it I fixed the issue it was the android webview that went disabled after enabling it it fixed the issue
[Magisk] Markeee:
I'm bumping this back up still looking for some help here
[Magisk] ktmom:
It sounds like you've been back and forth installing/uninstalling. I would dirty flash the ROM, then flash the Magisk zip in recovery. Make sure to save the recovery log before rebooting.

If there is still a problem, repeat the process using the canary build (bleeding edge/debug), again saving the log in recovery before rebooting.

If you still have trouble, post the recovery logs and the boot.img here or in the canary thread.

The error is indicating an unsupported image format, which is a problem with the boot.img.
[Magisk] JamesKinds:
I just wanted to say thank you. I did as you suggested and simply dirty flashed 20.0 in TWRP, cleared Dalvik and rebooted.

I am now back on magisk 20.0 and indeed the root issue for new apps that I was experiencing has been rectified.

I'll stay on 20.0 until a stable update >20.1 is released.
[Magisk] Markeee:
Ok tried all your suggestions Dirt Flashed clean installed and everything else i could think of nothing seems to work

keep getting the magisk failed to install error in Magisk manager

Heres a copy of the failed install log from canary build bleeding edge debug. The boot.img file is to big to upload the system is saying here
[Magisk] francwalter:
Hello anybody knows if the system is changed, if I uninstall (delete) a bloatware (system) app, like e.g. Youtube?

I have made an update (1st december 19, on my Xiaomi Mi A1) and now I have Youtube and other bloat-apps on my phone.

I had to delete it from /system/app/ and now I fear that the next system update won't allow because of it.

Will it effect a system update?

When the next update will come, I will try to uninstall Magisk as it is recommended and reinstall on the other slot before reboot, like it is recommended, so I won't need to flash it again etc.

But will the update run, when some system-bloat-apps are missing?

Thanks

frank
[Magisk] Wolfcity:
That depends on the manufacturer but in most cases even mounting system r/w is enough to let an OTA fail. In your case the size and checksum of

/system has changed now and I'm pretty sure that these parameters are checked when an update comes in. I would recommend to do those things systemless with an app debloater module in the future.
[Magisk] Goncalo29:
Hello guys, need some help.

I've installed everything normally, but I never get prompted to allow apps to use root (tried Adaway, SDMaid), on Magisk Manager log it always shows that the root request was denied.

Even though some apps (like my bank account app) detect that the device is rooted.
[Magisk] francwalter:
Thanks.

But each update of Youtube etc. would change the checksum, aint it?

What "App Debloater" do you mean?
[Magisk] Wolfcity:
Magisk module, see attached screenshot.

There are several things that an OTA update will check before installing, as I said it depends on the manufacturer, sometimes it's enough to mount /system.

Btw, as far as I know the updated parts of an app from playstore go to data/app.
[Magisk] MightySashiman:
Can confirm UBS Access app detect latest stable and canary releases of Magisk (with magiskhide and app renamed). Damn it.
[Magisk] ktmom:
Is this ROM pre-rooted? Zip the boot.img and see if it will upload. If not, you could put it on Google drive and provide a link.
[Magisk] AndyBury:
Hello, I did an update to Android 10.3 on my Oneplus 6t last night, and since then every time I boot magisk manager opens on the screen.

I checked the log and don't understand why I have:

--------- beginning of crash

12-19 16:47:35.651 710 3165 I Magisk : ** boot_complete triggered

12-19 16:48:02.627 710 718 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[7564] UID=[10023]

12-19 16:48:16.858 710 718 I Magisk : proc_monitor: [com.grppl.android.shell.CMBlloydsTSB73] PID=[9652] UID=[10160]

12-19 16:49:00.589 710 718 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[12528] UID=[10023]

Could someone please let me know what is going on and how to fix it.

Thanks in advance :good:
[Magisk] ktmom:
If I'm not mistaken, this has to do with a broadcasts problem. Try the canary build.
[Magisk] Crowbro:
Hi

I'm running magisk 17.1 with 5.9.1 manager and I want to update to the latest magisk version. When I install the latest manager version, the app crashes every time I open it. I think it is because the latest manager isn't compatible with the current magisk version on my device which is 17.1. What's the other way to update magisk since there is a huge gap between the magisk I'm running and the latest one? Or how can I uninstall the current version so that I can install the latest manager version and magisk subsequently?

Thank you
[Magisk] Markeee:
Thanks for the help I was hoping maybe was a simple as that just pre-rooted so wiped and did a clean install looked around see if Magisk manager was already installed but not so I installed manager and same issue Magisk manager showing magisk not installed and all attempts to install from with in manager fail

Heres the boot.img
[Magisk] ktmom:
[MENTION=4544860]osm0sis[/MENTION] can you help here? The install is failing with a unsupported format error.
[Magisk] AndreyAleks:
Sorry if it was earlier, is the android 10 supported?
[Magisk] FullWipe:
Sure!
[Magisk] Wolfcity:
You didn't wrote what device you have.

Normally the magisk manager is included in the magisk.zip so if there's a TWRP for your device you can uninstall the manager and flash the magisk.zip through TWRP.

If you want to uninstall magisk before to make a clean start, for every magisk version there is a fitting uninstaller:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post68966662

Run it and flash the magisk.zip afterwards.
[Magisk] Markeee:
Thanks for the reply

I thought I said in my original post to clarify I"m on a Pixex C Tablet flashing a MoKee Pixel C Android 10 rom

I'm flashing latest Magisk-v20.1 and even tried a new beta -v20.2 also using latest MagiskManager-v7.4.0 along with latest Twrp.

Manager is not included in the magisk.zip its a separate install as far as i know ?

I've tried the uninstaller flash in Twrp and fresh installs and everything else I can think of still no go