yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Netflix downloads, installs and launches fine on one of my devices with the latest unoffical 19.4, ianmacd-2019061203 build. It is the same for one of my same devices with the latest Canary debug build on it. However, I do not have a Netflix account to test it out. I prefer not to use the free trial until I actually consider signing up for it, though. I am on the latest Google Play Services beta 17.5.26.
[Magisk] duh1:
Issue is with unlocked bootloader, Netflix no longer appears in play store search and if you go there via link... https://play.google.com/store/apps/details?id=com.netflix.mediaclient

it indicates our devices are incompatible. Clear play services/play store cache, then what do you see there...
[Magisk] martyfender:
Of course if I clear that data the play store app will show my device as uncertified. I have done that in the past and the only way I got the certification to show true again was to uninstall all Google Play Services updates in app settings, 3dot menu in the upper right, then let it update again. Then it eventually showed my device as certified. By eventually, it can take several hours to show up certified. If you can't uninstall the updates then you have to turn off device administrators in Android settings, security, temporarily. Without clearing that data I can go to the link you provided and it shows neflix installed and I can click on a link showing which of my devices are compatible with netflix and all of them are. They are Nextbook Ares 8A tablets Intel x86, Android 6.0.1. I do not want to clear the data as you suggested as it is somewhat of a pain to get it recertified.

Magisk Hide hides the status of my unlocked bootloader just fine on all 5 devices. Have you tried toggling Magisk Hide off then on in settings?
[Magisk] xunholyx:
The canary and canary debug channels only show to select on the canary builds.

In stable or beta builds, they do not show as an option to select.
[Magisk] Ballman729:
Updating of Magisk

Hey guys! I recently rooted my note 8 and majority of the modules weren't showing up in the downloads or modules section and magisk hide doesn't work for this one delivery app which I use (I send food)

I've looked over the Xda threads plus magisk and did as told but it doesn't work. So since there's updates to magisk already, would it be safe for me to update magisk and would it cause me to have a boot loop?
[Magisk] duh1:
I didn't say data, I said cache -- so you wouldn't see the cached version of the Netflix page.

In any case. I clear store/services data all the time without harm or loss of certification. Just have to clear Download Manager data as well to get play to repopulate My apps.
[Magisk] gipsy.danger:
i have different device than yours with custom rom loaded. when i upgraded the Magisk to 19.3 everything was fine because i had my play store certified but then i decided to update my play store to test the new UI, i cleared the data and cache and then the issues started. the play store uncertified my device.

i tested cts and it failed. i downgraded my rom but still same issue so i flashed magisk 19.2 and everything works again.
[Magisk] martyfender:
When I clear cache, only, as you stated, on a device without Netflix, in Chrome, it opens the playstore app and gives me the option to install the app. If I install it and go to your link again in Chrome it again opens the playstore app and shows that it is installed and give me the option to open or uninstall it.

In Firefox it shows that the app is installed when it is not. Again, it installs fine on that third, bootloader unlocked device, just like the others.

Have you tried a fresh install of your rom and Magisk? Maybe someone in your device forum can shed some light on this.
[Magisk] ashyx:
Did you actually re-hide play store? It has been posted many times in this thread, if you fail cts with 19.3 then root is being detected because Magisk hide isn't working. To fix it just disable then re-enable Magisk hide then ensure Play store is hidden, as considering you've updated, it will no longer be hidden.
[Magisk] RandomPooka:
That happens to me with PoGo every time I restore my system after a test flash of a ROM
[Magisk] Mardukas:
Hello, Magisk update 19300 is up for some days now but I haven't installed it yet (running 19100 now) because my latest try on installing an update through Magisk Manager app left my phone stuck on boot loop. My phone model is Motorola Moto G4 Plus XT1640, running 8.1.0 stock Android (TWRP backup flashed) and ElementalX G4 3.01 Kernel.

When rebooting after installing the update, the phone started to vibrate for a long period and kept stuck on logo, forcing me to turn it off. In the end I had to flash system image again through TWRP backup, making me lose everything that wasn't backed up, like saved games or app settings. It's working normally as of now, so as Magisk, but I'm not sure what's the best way to update it (or if it's needed whatsoever). Could someone point me towards the right directions, please?

Thanks in advance.
[Magisk] darfri:
Well this 19.3 has the same issue. With Smurfkernel or without.

Still back to 19.1 :S
[Magisk] LoganDark:
On my SM-N900V (Verizon Note 3) running the SEPL1 stock ROM, attempting to flash Magisk always results in an "Android is upgrading..." and then a suspicious lack of Magisk. I think the OS is reinstalling itself whenever I try to install Magisk. is there any way to prevent that?
[Magisk] nebula9:
I'm running Magisk 19.3 on an LG V30 with crDroid. Unlike with my Pixel, everything "just works" — Google Play store shows Netflix in searches, Google Pay works, etc.

So, my questions are these:

1. What detection method does Google Play use to tell whether or not your device should be able to see Netflix on the store? It's not safety net or ctsprofile, for sure. And it's not the same as Google Pay's method of checking the attest database.

2. I checked the attestation states in GMS' folder and they were set at 10. So why am I not seeing any trouble?
[Magisk] Didgeridoohan:
Play store certification status.

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] nebula9:
That's what I thought. But on a device which has always been magisked and has always passed safety net and ctsprofile since first boot into the ROM, and on which the play store has shown ostensible certification, I still can't see these apps. (pixel 2 xl, on stock + many custom ROMs) And on the CrDroid v30 I have no problems.
[Magisk] Didgeridoohan:
They might of course have added something else as well. There's been scattered reports but nothing definite...
[Magisk] casouzaj:
Sony Xperia Z5 Compact phone here, running a stock Nougat ROM. I submitted its kernel to the rootkernel tool in order to include my previously backed up DRM keys and have Sony RIC deactivated, then rooted it by the stable Magisk v19.3 release. The latest Netflix, installed by Pay Store, just works!
[Magisk] Krishna khonder:
My mobile no root please help me sir
[Magisk] sdamark:
Please follow forum rules and instructions to file a proper report of your issue.
[Magisk] duh1:
Good questions -- I wouldn't be surprised if Google and Netflix are testing out some new methods of detection...
[Magisk] scottfreeze:
Have you made any further progress on this? I'm also experiencing reboot to recovery (with try again and factory reset as my only options) after installing Magisk 19.3 on a brand new Pixel 3 with the June security update. Reverting to stock boot image allows booting into system. Core-only mode (/data/cache/.disable_magisk) did not rectify the problem, nor did installing earlier versions of Magisk (tried 19.0 and 18.1).

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

Did you ever solve this? I'm seeing the same thing after installing Magisk 19.3 on a brand new Pixel 3 with the June security update. As you noted, reverting to stock boot image allows booting into system. I also tried starting Magisk in core-only mode (/data/cache/.disable_magisk) which did not rectify the problem, nor did installing earlier versions of Magisk (tried 19.0 and 18.1).
[Magisk] ApeironTsuka:
I did solve it, but in my case it was a module causing the issue and forcing core-only mode worked. Gave up trying to do it via init.rc and switched to compiling Magisk myself with core-only mode forced.

In your case, try pulling a logcat during boot (adb wait-for-device && adb logcat > logs) of it failing and see what, if anything, it shows. Look for mentions of "RescueParty: Noticed 1 events for.." and what error preceded it. Will also give you an idea of how far into booting it gets.
[Magisk] Yippee-ki-yay:
I just installed the magisk manager update (7.3.0) and it does not show many recent modules to download.
[Magisk] lm089:
Had the same. Closed the app through settings >> apps, and deleted app cache. After rstart of the app all modules where shown again.

BUT:

No matter what I do: the Superuser view is empty now. Even rebooted phone, app still doesn't show SU apps. There should have been be quite a list, and the SuperUser log was proving that.

So I uninstalled 7.3.0 and re-installed the previous version (7.2.0) which luckily I still have. Now SU view is showing correct data again.

Magisk log doesn't seem to hold any info about that, but if a log is needed let me know
[Magisk] Fentadroid:
Any idea if is there any way to delete modules without root without wiping? Edge plus magisk module is the reason i cannot root anymore on my pixel 3a. If i flash patched boot.img the phone bootoop... And i guess that module is the reason of this.... I didn't know i had to delete the module before update to june security stock rom... I would like to compile magisk forcing core-only mode but i really don't know how to do that ? can you tell me exactly how to pull a logcat during boot? I really would be happy....
[Magisk] zzz2002:
What the default hide setting for Google play. I inadvertently cleared all the setting. I had thought of just turning the all on but this is not the usual default.

Tia
[Magisk] JudgeDread11:
I never touched it, so I think this is the default.
[Magisk] JudgeDread11:
I had the same problem with the superuser view.

I fixed it by deleting data/adb/Magisk.db and restart.

After this you will need to grant su rights to your apps again.
[Magisk] Fentadroid:
Yes.

I mean... Now, i know the reason (99%) why this happen with my Pixel 3a: active edge plus magisk module.

Now i'm not rooted anymore and without a TWRP i cannot delete /data/adb/modules and /data/adb/Magisk.db.

So, i guess i have 2 possibilities

1) wipe everything

2) wait for a TWRP.

If you have any idea.....

---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------

The problem is that after uprading to june security update i've lost root and flashing a patched boot.img wont solve the issue.

TWRP doesn't exist for Pixel3a

So...... there is nothing i can do but wiping the phone or wait for a working twrp.

EDIT: i've attached full logcat.

If someone could help me to know the reason why my phone fails to start i will be happy :)

Thanks in advance.
[Magisk] scottfreeze:
OK... Looking for any help at all here! Can't seem to root my brand new Pixel 3 with June security update using Magisk. Here's what I've done to try to identify the problem:

Performed a factory reset (bootloader already unlocked), skipped the setup in order to enable USB debugging, then immediately attempted to install Magisk 19.3 on the freshly reset Pixel 3 (June security update) by booting into TWRP 3.3.0.0 and flashing Magisk from there.

The result was a 1-2 minute bootup attempt, after which the phone reboots back to Android Recovery with the message "Can't load Android System. Your data may be corrupt..." and the only choices are Try again or Factory data reset.

Using the command that ApeironTsuka provided below, I captured a logcat of the boot process. Actually, the actual command he provided gave an "access denied" error, so I just ran "adb wait-for-device && adb logcat" and copied the output from the command prompt window, which led to the attached logcat that does indeed contain "RescueParty: Noticed 5 events..." but I am in over my head when it comes to analyzing the logcat for the error that caused it.

Can anyone provide any further insight?

Please help!

Edit: I can provide a more complete logcat if needed... I figured out why I was getting access denied before.
[Magisk] lm089:
True. For it even worked with > uninstall V 7.3.0 > re-install V 7.2.0 > update to V 7.3.0 again

Whatever...
[Magisk] Fentadroid:
I've posted my logcat file a couple of post before.

Did you compile a magisk manager version that allow me to patch a boot.img file forcing core-only mode? No TWRP for Pixel 3a yet and I don't know how to modify /data folder to erase modules....
[Magisk] Xdevillived666:
Tried this but when going to downloads to search for modules it says no modules found. Any advice ?
[Magisk] ApeironTsuka:
I had the same module causing the same issue. Have a Pixel 3a XL, so was in the exact same boat. All that I found that worked was to compile Magisk manually (after altering it to force core-only mode) and manually patch the boot image. The crude steps being...

download Magisk source via git
download FrankeNDK (linked from the Magisk readme) from git
follow the Magisk setup steps regarding the ANDROID_HOME and ANDROID_NDK_HOME environment variables
comment line 609 of Magisk/native/jni/core/bootstages.cpp (starts with if (access(DISABLEFILE... .. depending on when whoever is reading this stumbles on this, it could be a different line. Just ctrl+f for DISABLEFILE and you should find it)
build.py stub
build.py binary
grab the boot image tools from https://xdaforums.com/showthread.php?t=2319018
use split_boot to unpack magisk_patched.img
delete magisk_patched/ramdisk/init and copy Magisk/native/out/armeabi-v7a/magiskinit in its place (be sure to name it init)
use mkbootimg to create a new boot image out of it
boot into the bootloader and use fastboot to boot it directly

I could upload the magiskinit binary somewhere (since the whole compile process ate up ~5gb of disk space for the sake of a 300kb binary) if you want to skip to manually patching a boot image. I don't know if the one for a 3a XL would work on a 3a (even if it's the same June update), or I'd offer uploading that instead. Suppose you could give it a shot.
[Magisk] Fentadroid:
That would be nice... i can try to fastboot boot that without flashing it first to see if it works :)
[Magisk] zzz2002:
Thanks. I also adopted you setting for the play store.
[Magisk] mcwups1:
Hello.

Curious as to why I can't see what's been given root access? On 19.3, and 7.3 respectively.

Thank you.
[Magisk] mkdante381:
Magisk Manager 7.3.0 is bugged:

-Afer hide Magisk Manager is not restoring properly all settings from Magisk Manager.

-Magisk hide not work with apps on adopted storage with 7.3.0 Magisk Manager. Tested on 7.2.0 with hiding Magisk Manager and work.

Why this is in stable??
[Magisk] lm089:
Have you tried removing Magisk.db as described here?

For me it also helped to uninstall 7.3.0 then re-install from scratch
[Magisk] gil80:
Using the last version of magisk, saftynet fails and magisk hide fails as well.

The superuser list is empty.

I can't upload the log zip file to the forum.

Is it a know issue?
[Magisk] mcwups1:
No, I haven't. This is a long thread, my first inquiry in this thread, and the search function in the app isn't helpful.

Thank you for the information.
[Magisk] lm089:
Empty SU list is a known issue (see one up from your post, and a few more before that).

I hadn't checked safetyNet before, now the query is showing valid results.
[Magisk] darfri:
I can confirm that 7.3 is bugged at least in Downloads emptiness. No other bugs found so far...

Of-course it might be because I am using Magisk 19.1

19.2&19.3 freeze systemui, launcher etc (live wallpaper survives smoothly)

at the very end of boot sequence. Anybody else having this?

Anyway this happens on oneplus 6t with latest havoc os ontop oos
[Magisk] gil80:
Uninstalling and reinstalling fixed some of the issues.

Saftynet passes but magisk hide is bugged.
[Magisk] mrsubway:
For anyone not seeing downloads:

Download the Magisk Manager 7.2 from their site. Won't let me post the link.

Uninstall Magisk Manager 7.3. Do not reboot. Install the 7.2 apk, open Magisk Manager and update to 7.3 again. Fixed it for me.
[Magisk] JudgeDread11:
Do the download stay visible or do they disappear after a while again, like clearing the repo cache from within settings.

Clearing the repo cache in Magisk settings and then refresh makes all downloads come back again, but I need to do this regularly.

---------- Post added at 02:34 AM ---------- Previous post was at 02:23 AM ----------

If your su list is empty you can delete data/adb/Magisk.db and reboot. After that you will need to give the su permission to your apps again, but they will show up in the list. Also Magisk hide needs to be reconfigured.