yashsingh1/xdaforums huggingface dataset:
[Magisk] ACHILLES R32:
I updated my pixel 2 to the Android 10 stable release this evening .

First thing I did afterwards was root with magisk .

I pulled the boot file, patched it and flashed it.

I opened magisk everything is checked , used Root check app. That came back positive.

However when I try to modify my host file and install my custom host file I get error messages saying " Can't delete file" .

I tried both root explorer and solid explorer both apps have root access . But can't modify the system files.

I'm starting to thing that I'm getting a false positive on root or something has changed in Android 10 and we can no longer modify system files.

I tried both the stable version and canary version builds of magisk . Both say that I'm rooted but the issue persists .

And im not running twrp, I just had systemless root and stock recovery before and everything worked flawlessly.

Is anyone having a similar issue?

Thanks

Sent from my Pixel 2
[Magisk] JudgeDread11:
As mentioned several times before now. You can not directly modify the system partition. You'll need to do it through a module.
[Magisk] zestar_77:
Pixel 3a XL. Android 10

Magisk Canary, patched boot.img and flashed it. reboot device and ...

Magisk manager says magisk is not installed. Uninstalled and reinstalled magisk manager, no change.

I've been reading this discussion and so I did make sure both advanced options where checked in magisk. I'm not sure what I'm missing here.
[Magisk] ACHILLES R32:
Thank you for the reply, I should have looked through the thread. I ended up installing energized module . No more ads

Sent from my Pixel 2
[Magisk] martyfender:
Did you go to Magisk Manager settings, click on the systemless hosts option, you will see a toast: added the systemless hosts module, briefly. Then you must reboot for the changes to take effect, just like any other module installed.

If that doesn't work, I would say that it is a problem with the using this with the new Q, since the system is apparently not writable, although Magisk should be doing it systemlessly. Anyone having better info to clarify, please correct me if I have any of this wrong.
[Magisk] ACHILLES R32:
Correct I selected systemless hosts, rebooted , installed energized pro module , rebooted . Copied hosts.gz file to energized folder in SD card.

Ran the script in termux. And rebooted the phone one more time

Sent from my Pixel 2
[Magisk] Strephon Alkhalikoi:
Well, I have a properly functioning Magisk so I simply uninstalled them using Magisk Manager. There should be a hamburger menu (three bars) at upper left. Also, I'm not using Canary versions of Magisk.

On a side note the sound mods I use I reinstalled after getting V4A running again. YouTube Vanced and Quickstep however I have to wait on. The former installs fine but does not appear at all in my app drawer. The latter generates errors on install and throws up a script error on boot.
[Magisk] RebelLion_:
I just updated to Android 10 on my Oneplus 7 Pro (Intl, unlocked, carrier T-Mobile) and first issue I noticed was Magisk Hide no longer functioning as expected. I play a game called Utopia Origins that persistently checks for root, and it worked right until the update. It is worth noting I also play Fortnite Mobile and it seems to function fine still, so this is an isolated event but nonetheless the only change was an update to Q/10. In that case, I am led to believe there is an update needed to address the change and have decided to notify [MENTION=4667597]Didgeridoohan[/MENTION]. If needed I will attempt to collect logs
[Magisk] palmbeach05:
System as root anyone? Or does no one use google to find out the changes? Magisk will need to be updated by topjohn to enable compatibility.
[Magisk] saccentekennedy:
Magisk Hide suddenly not working on my banking app this morning... Not sure why. The app updated a few days ago so I rolled back to an earlier version of the app and I'm still having the same problem. I'm getting two checks on Safety Net passing. I've tried activating and deactivating Magisk Hide, starting and restarting, etc. Nothing.

Anybody having a problem with Magisk Hide all of a sudden? I'm on a OnePlus 6T on Open Beta 17. Nothing else has changed.
[Magisk] coolguy:
How to install on fresh install of Android 10 betA 1 on OnePlus7 Pro? Since twrp doesnt install
[Magisk] zgfg:
Pls scroll back and read previous posts, it has been extensively discussed (here and in the other Magisk thread, Canary) last days about Q.

And there is another method (without installing ZIP through TWRP), patching and flashing the boot image, discussed in this thread and described in Magisk docs on GitHub.

However, Q is new and there might be specifics with your phone (it was mostly discussed so far about Pixels)
[Magisk] warrencoakley:
Read my posr few pages back and retry. Confirmed working

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Read my post few pages back and retry. Confirmed working

---------- Post added at 08:41 AM ---------- Previous post was at 08:35 AM ----------

Thanks. I decided to use the file explorer in TWRP to remove the modules that have not been updated and was causing a bootloop. Can confirm Valance YouTube is working with no issues.

---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------

Thanks. I decided to use the file explorer in TWRP to remove the modules that have not been updated and was causing a bootloop. Can confirm Valance YouTube is working with no issues.
[Magisk] Strephon Alkhalikoi:
I don't have YouTube automatically update but the behavior I was encountering was consistent with a regular YouTube update being applied over Vanced. So I updated YouTube through the Play Store then uninstalled the update. The Vanced icon popped up. Weird.
[Magisk] zgfg:
It is enough to install Vanced, without prior installing/deinstalling YT.

But auto-update for YT must be disabled in Playstore because every new YT version will override Vanced (YT will sow as 'installed' once you install Vanced)
[Magisk] SchmilK:
I've been trying to get fortnite working on my op7pro since I got it 5 days ago. Even straight out of the box no root or unlocked bootloader i was getting kicked after jump.

Now I've uninstalled and reinstalled a few times with magisk in core mode, magisk name scrambled, hide root for all root apps, hideroot for fortnite installer and fortnight and system ui. Still can't get past the jump. I must be missing something else now
[Magisk] JudgeDread11:
If even without magisk it's not staying then it's not caused by magisk and you are in the wrong place to ask for support. You should find help on the game's webpage, Facebook page or is own forum if it has one.
[Magisk] SchmilK:
Epic support said they fixed the random kicking problem yesterday, but that was after I had unlocked and rooted my phone so I never got to try it unrooted. Figured someone with the same phone could have a tip.

*Edit*

Moved to Canary channel and everything worked.
[Magisk] zestar_77:
[/COLOR]

Ah thank you. I didn't switch the Chanel off of Canary (debug).

Now that I switched off of that it's working.
[Magisk] Strephon Alkhalikoi:
Reading comprehension failure? My post clearly says that I don't have YouTube automatically update. Therefore, I really don't need the lecture about stuff I already know. While I don't know why my device exhibited this particular behavior when I don't take updates, the fact remains that it is fixed.
[Magisk] Ch3vr0n:
Thanks that worked. First attempt failed, probably because after setting update channel to canary it didn't 'see' an update. 2nd attempt (manual refresh of magisk update saw a 19.4 version) that one worked (a long with the preserve setting)

A double bonus is after this update, I was able to update my 'old' Netflix 6.26 build to the latest version and it didn't bug out!

Problem solved for me, for the moment.
[Magisk] palmbeach05:
Well its official, android 10 is out, and the reports and complaints that "my magisk and/or magisk module has broken" are rolling in. Lmao
[Magisk] Badger50:
Who'd a thunk that would happen! :laugh:
[Magisk] demonoidmaster:
Edxposed is xposed, it's no different, however there's a few more options you can use, like it's whitelist option etc

Taichi works differently than xposed as it doesn't modify files
[Magisk] Ch3vr0n:
Ya think, at least it was relatively easy on Pixel devices I've read here (and my own). I doubt it will be as easy for non-pixel (/old Nexus) devices.
[Magisk] hfam:
Heya All!

I've read back a ways in the thread and this seems to be the only Pixel 2 reference regarding the Q update (lots of 2XL, 3, and 3XL).

I also have a Pixel 2, and usually perform updates by flashing full system image (remove -w), boot into phone, MM to patch new boot, flash patched boot. I really only use it for root, no modules.

As this next update is Q, can you confirm no issues with the update itself on Pixel 2? I see they've made system unable to make r/w in Q, but I've never made any changes to system anyhow so I don't think that's an issue for me.

I'm currently on a Pixel 2, no TWRP, August sec update, Magisk 19.3 with no issues. Hoping the Q update will work essentially the same as previous updates. Lastly, do I require Canary 19.4 or is 19.3 working with Q on Pixel 2?

Thanks for any advice!
[Magisk] palmbeach05:
So you want android 10 to magically work with your magisk? You can sit tight and wait for it to be updated so that it is compatible, esp as the source code was only just released.
[Magisk] novren:
Hey, sorry if this has been asked lately, I used the in-thread search and couldn't find anything.

I can't manage to get Netflix to work since today, or yesterday. It didn't update, and when I checked on the Play Store, it said that my device was no longer compatible with this app (my Netflix installation was from Play Store). So, being a stupid sandwich as I am, I updated it from the Netflix website by downloading the .apk. Now I am getting a "This device is not supported by the app" message as soon as I launch Netflix.

I've cleared cache and storage of: Play Store, Google App, Netflix.

I've reinstalled Netflix.

It has always (including right after reinstalling it and before opening it) been checked in my Magisk Hide list.

My current apps in Hide are: 3 banking apps (one of which, BTW, has been telling me lately it won't allow me to login via fingerprint since my phone does not comply with safety measures), Play Services, ConfigUpdater, Health Services, Digital Wellbeing, Google, Google Backup Transport, G One Time Init, G Partner Setup, G Play Store, G Services Framework, Market Feedback Agent, Netflix, X Google Enrollment.

I've also tried hiding Magisk Manager (via the option in the settings), and I've renamed every Magisk file/folder to something like Magick.zip, etc.

My phone passes SafetyNet (both checks)

This is all on a Pocophone F1, running AOSP Extended, latest official version, Android Pie.

Attached logcat.
[Magisk] RebelLion_:
All I had to do was hide magisk manager, fortnite and fortnite installer and it worked like magic. The other game (Utopia: Origins) seems to have a different check(s) in place, since nothing short of uninstalling Magisk satisfied it.
[Magisk] hfam:
The only magic here is you managing to use a few 3 syllable words, kid

Save your unclever, unhelpful asshattery for Facebook, and learn to read for comprehension.
[Magisk] RebelLion_:
And what exactly are you saying lol. Idk if that was meant towards me or in general, I tried looking up what would be different but A-10 is too new so I'm assuming its something that topjohn needs to workaround or fix in an update
[Magisk] ACHILLES R32:
You can use stable release. You only need magisk modules if you plan to modify system files

Sent from my Pixel 2
[Magisk] palmbeach05:
That was directed at anyone, not you specifically. Android 10 comes with system as root, which is going to affect how magisk is flashed to a device and all the fun that the installer script must do in order to get the full compatibility. And thats not taking into consideration that twrp will change because of sar.
[Magisk] hfam:
Outstanding, thanks for the quick reply brother!
[Magisk] martyfender:
Topjohnwu recommends using the Canary build with Q, at least that is what I gather from reading his latest twitter post:
[Magisk] hfam:
Ahhhh, nice catch, thanks [MENTION=8126387]martyfender[/MENTION]! As always, I'll report back with my results and methods.

I'll have to proceed over the weekend, I've got "digital only" tickets (8th row seats!!) for Iron Maiden in Portland tomorrow night!! W0000!! Don't want to mess that up! ?

Thanks again brother, much appreciated!!
[Magisk] Yu-4IL:
Can someone help me?

I upgrade my Oneplus 7pro to Android 10 without disabled all modules. But some modules will cause boot-loop in Android 10. So I got boot-loop when I patched magisk 19.4. In logcat I found that it was caused by riru module. So can I disable the module without root?

ps. Twrp recovery is not available on the Oneplus 7pro Android 10 to boot.
[Magisk] ktmom:
Safe mode?

Actually, if your boot looping, you can't get to safe mode. I'd boot to recovery and factory reset or dirty flash (without -w flag) in fastboot.
[Magisk] eelik:
Thank you very much jcmm11! Upgrading to canary seemed to do the trick. I was left with the I was on a new version merely a few builds behind Canary, with nothing too exciting in the release notes, but turns out I was a full minor version behind (19.3->19.4). I now pass RootBeer Fresh with success, and my application works!
[Magisk] novren:
Forgot to add, all checks are green in Rootbeer.
[Magisk] edzamber:
Hi

Have a look Here

https://xdaforums.com/showthread.php?p=79618057
[Magisk] Yu-4IL:
Thx. So all I can do is factory reset or flash the stock boot image without root.
[Magisk] warrencoakley:
Handy YouTube video for rooting on Android 10

[youtube]cnMYmvKArF4[/youtube]
[Magisk] novren:
For the moment that works but that is a workaround. I'd really like to know why I'm getting that message. Thanks anyway!
[Magisk] Didgeridoohan:
So far, I've mainly only seen that reported on Pixel devices and there the consensus has been that it's somehow caused by the unocked bootloader (but I haven't seen, or actually looked for, any substantiated information about that).

Possible culprits could be something about the bootloader state (as above), your ROM, or whatever... It's not unheard of, but I've seen no proper solution.

Disclaimer: be really carefull if you decide to start testing locking your bootloader since it could easily mean you end up with a non-booting device and no way of fixing it...
[Magisk] edzamber:
I got same issue here on S9 G960f since May, my device is incompatible with Netflix. It happens subitly without any reason with same Rom usage (my own Rom). Only way is to use Split apk Netflix version
[Magisk] fc_themaster:
Magisk Hide doesn't work with Android 10.

I'm on Oneplus 7 with Magisk 19.3
[Magisk] novren:
Netflix must have simply added another detection method, because it is the same rom I was using (it was test-keys earlier and it is now release-keys) with magisk and magisk hide set up in exactly the same way. The only thing that has changed is magisk.

And come to think of it, the release-keys thing might be the culprit. But it would make way more sense the other way around.

Don't worry, my BL stays unlocked for the foreseeable future. If I were to lock it I'd restore a full miui rom and recovery first, but I doubt I'll ever do it.
[Magisk] Danny94:
EDIT: OH everytime i reboot i need to untick and tick magisk hide again to pass everything. Any fix there ?

I installed on Samsung S3 Neo (i9301I) this rom:

https://xdaforums.com/galaxy-s3-neo/general/dev-lineage-os-14-1-s3-neo-t3678522

Im unable to pass safety net.

ctsProfile: false

basicIntegrity: false

On RootbeerFresh i got following problems:

-su binary

-su exists

-root native

-magisk binary

I tried to run:

-unSU Script zip

-installed supersu apk and did a complete unroot

-tried a lot different roms (all roms and kernals base on the same rom)

-changing fingerprint in build.prop https://xdaforums.com/galaxy-s3-neo/help/fix-safety-net-cts-profilefalse-custom-t3786849

-I used magisk core only

-[Magisk hide is active] Ticked all apps related to google

-Hide magisk manager

-No modules installed

-Have disabled developer options

-Have disabled Usb debugging

How i can make this device pass Safety Net.
[Magisk] ktmom:
You might try booting to recovery and using ADB to remove the module. It's harder to recover from errors when it's a spanking new major release and all you have is stock recovery.
[Magisk] Yu-4IL:
It seems that I must have a twrp to remove activated modules because I cannot access su from stock recovery even if the magisk-patched image has flashed.
[Magisk] KapilNagpal01:
Use Magisk Canary 19.4. Everything will be fine
[Magisk] ktmom:
Was ADB root enabled in the Magisk manager?
[Magisk] SchmilK:
Moving to canary branch (and a fortnite update maybe helped) but now it's working.
[Magisk] Yu-4IL:
I got boot looping when I flashed magisk patched image. So I couldn't see the magisk manager settings page with root.
[Magisk] elmu:
hmm...magisk leaves by itself for me? i flash magisk again but after about day root leaves by itself.

i use latest stable 19.3. oneplus 6+oos 9.0.8.

can someone help me?:D
[Magisk] guest4711:
It's a known issue occurring on some ROMs. You may try to compensate by using a script to toggle MagiskHide off and on again.

I had best success using the init.d emulation of KernelAdiutor and running a script like

#!/system/bin/sh
/sbin/magiskhide disable
/sbin/magiskhide enable
[Magisk] RebelLion_:
Lol really. Cause I have TWRP on Android 10 on my Oneplus 7 Pro GM1917
[Magisk] Yu-4IL:
If you flash or boot twrp image from stock, you will be stuck in the fastboot page. XD
[Magisk] vonDubenshire:
Get rid of TWRP on there, you're gonna screw up now.

TWRP isn't needed, it's easier to do it without recovrey
[Magisk] martyfender:
Are you pehaps confusing adb root with adb shell, then typing su? At least when I do this on my devices, I get a Magisk root prompt to approve. The adbd is by default, made to not allow true adb root. Adbd insecure, by [MENTION=631273]Chainfire[/MENTION], is an app in the past, that allowed you to do this, but it doesn't work on newer Android versions.

I have a hacked version of it, from the adbd insecure thread, that works on one of my Android 6.0.1 tablets, which also must run in permissive selinux mode, using Selinux Switch, to work.

I believe in userdebug builds of Android and some custom roms, one can use adb root.
[Magisk] JudgeDread11:
Make sure magisk manager is not being killed in the background by Android battery optimization or any other battery saving feature from apps or ROM.
[Magisk] martyfender:
Try this guide:

https://dontkillmyapp.com/oneplus

And also here for other devices with over aggressive battery optimization:

https://dontkillmyapp.com/
[Magisk] GoJo ^^:
Hello, could somebody tell please how to get Magisk to work on lollipop? I mean, it installs fine, module has well.. But barely any of them will actually work! I'm on a x86 tablet. Let me know, thanks!
[Magisk] Arden144:
If Magisk installs, then the issues have nothing to do with it. You're using modules not for your device or android version
[Magisk] KapilNagpal01:
I am on OnePlus 7 Android Q Open Beta 1, I had successfully installed Canary 19.4 all was working well.

But I flashed a zip for pixel launcher and went into bootloop. I reflashed my stock OS OB1 and could boot. Now when I booted Magisk was not installed so used Magisk manager and patched boot image but after flashing it I enter bootloop.

I flashed boot.img from fastboot and could boot to system again. But again when I try to install Magisk through patching info to bootloop.

My problem is our recovery is not fully working, I can install twrp to through Magisk but I am not able to boot through .img file in fastboot as it is not compatible to boot from fastboot and can only be installed through Magisk.

Please suggest is there any way I can install Magisk on this booted and fully working stock OS OB1. Or only solution is to reset, loose all data and start again.

Any help will be appreciated. Thanks
[Magisk] zgfg:
By flashing stock Boot image and back the patched Boot image - previously installed modules still remain on Data and get activated with Magisk

It's been extensively discussed and several times in this thread where and how to disable particular Magisk module or boot in the Core only mode.

Please check instructions on GitHub, I don't know what would be applicable for Q (I'm still on Oreo and device where folder with Magisk modules can be edited from TWRP), or you could only reset Data to remove the installed module causing the bootloop
[Magisk] KapilNagpal01:
No brother when I go fastboot and flash boot.img I am able to reboot. But then when I again patch the boot.img to reinstall Magisk and fastboot flash boot magiskpatched.img then I again get to boot loop.

Though on this stock Android Q open beta I was running Magisk successfully. But now I don't know what is happening it sticks to boot loop when flashed. I don't have working twrp to flash Magisk.

Something is interfering and not letting me boot with flashed patched boot.img.

Edit: Done bro. I again went to fastboot and flashed boot and system.img booth and booted. Flashed patchedboot.img again and I was able to boot this time. Magisk installed. Thanks all
[Magisk] FriendlyNeighborhoodShane:
So now that Q will have a ramdisk in boot again, I hope Magisk will start working normally, without a recovery, again?
[Magisk] GoJo ^^:
But the module states"from lollipop"!!
[Magisk] Didgeridoohan:
That's an issue to bring up with the module developer then (module thread, GitHub, or whatever means of contact is available).
[Magisk] aqwserf:
Hello,

I have a Pixel 3 on Android 9 (P3QA.190801.002) with Magisk 19.3 (19300) and Magisk Manager 7.3.2 (224). Since a few days, I'm able to upgrade to Android 10.

I was wondering if I could use the OTA Installation (available on topjohnwu's github) procedure to upgrade my phone and keep Magisk installed ? I successfully used it in the past and it's, in my opinion, the easiest way to do it.

Thank you !
[Magisk] elliwigy:
english...
[Magisk] elliwigy:
adb root can b easily enabled even with just a few prop values.. but yes, adb root and adb root shell are different.. some devices u just change ro.build.type to eng and/or ro.adb.secure=0 and adb root will work
[Magisk] Artim_96:
Nothing relevant there
[Magisk] JudgeDread11:
Yes like said, the module that caused the voorkoop in the first place it's still installed. So with a fresh bit image magisk isn't there and the module is not loaded. So you can boot. As soon as you install magisk the module will be loaded on boot. So you need to remove the module first before installing magisk again.

Search this forum on how to do that.
[Magisk] philipbuechler:
Awesome!

KapilNagpal, could you write more about how you did it? A lot of people have the same problem with the boot loop after patching boot.img and flashing it in fastboot. Did you flash other files? A step by step instruction would help a lot.
[Magisk] bitye:
Any workaround for 10 ROMs without SAR recovery?