yashsingh1/xdaforums huggingface dataset:
[Magisk] tramp20:
1. I uninstalled Magisk from the MM

2. I flashed Magisk 21.1 in TWRP

3. After boot MM says "Magisk installed: N/A"

I got this error with all canaries until now :(

To solve this I have to flash the original Magisk-v20.4.zip again, flashing the newer zips (e. g. Magisk-v21.1.zip which include the Manager too) will always fail.

I have several Z1c (with Lineage 17.1 and AICP 15.0, all Android 10) and they all show this behavior :(

The updater-script in Magisk-v20.4.zip and Magisk-21.1.zip are almost the same, only the newer one has a additional line:

blockdev --setrw /dev/block/mapper/system$SLOT 2>/dev/null

I am no programmer so I don't know if this could be important.

I attached the recovery.log after flashing 21.1.
[Magisk] pndwal:
Yes, I've seen reports of similar problems, but I've just gone back on discussion, and see your TWRP is v3.0.2-0, and your LOS 17.1 is Android 10, so I believe incompatible TWRP may well be your problem.

Nb. TWRP still does not support devices that shipped with Android 10 as latest v3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10. This version does, however, fix support for legacy devices that upgraded to Android 10, but retain the old partition scheme.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83725859

So you really need at least TWRP 3.4.0 to support Legacy device running Android 10.

If you can't obtain compatible TWRP, I'd be trying Patching Image w/ boot.img method (flash w/ ADB Fastboot). This is the recommended method anyway.

https://topjohnwu.github.io/Magisk/install.html PW
[Magisk] tramp20:
Ofc I have twrp-3.4.0-1-amami.img for my Android 10 devices (only 3.0.3 for my stock rom 5.1.1).

Once more:

If I flash Magisk-v20.4.zip then Magisk and MManager were properly installed.

If I flash Magisk-v21.1.zip or the canaries then nothing is installed.

I can repeat this for ever...

I attached two recovery.log files taken immediately after flashing Magisk.
[Magisk] pndwal:
Yes, that was initial fix. It causes a mismatch with model props which is enough to cause a fallback to Basic Key Attestation, but doesn't spoof a real device to achieve this, so device/OEM specific functions/apps etc are likely to fail.

Nb. Most are now using now using MagiskHide Props Config Force BASIC Key Attestation function which does spoof a real model, often manually selecting as close a device as possible (likely a later model from same OEM/series) to achieve this mismatch/fallback to Basic while improving device/OEM specific functionality vastly. :good: PW
[Magisk] xp99:
How do I Force BASIC Key Attestation with MagiskHide Props Config? The only way I found was to use the script that was posted here.
[Magisk] zgfg:
You run props in Terminal and read offered options - number 2 is called Force BASIC key attestation, exactly as that.

Don't you see it

If needed, there is XDA thread for MHCP, with instructions in the OP post #1, and a link to Github with more detailed documentation
[Magisk] pndwal:
You need to select options/configure in Terminal App after typing 'props'...

See OP (first link) and following documentation. :good: PW

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post76494810

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#usage

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] xp99:
I got it now. I did the following:

1. connected my pixel 3a to my computer via usb

2. opened up command prompt/powershell/terminal

3. ran 'adb shell'

4. ran 'props'

5. chose the option 'Force BASIC key attestation'

6. went with the default value

7. rebooted the pixel 3a

Only thing now that is not fixed yet is that google play app says my device is not certified under play protect certification.

Thanks for your help!
[Magisk] pndwal:
So sorry to assume you might have messed up! ;)

Barring pilot error (perish the thought), it may relate to this issue:

https://github.com/topjohnwu/Magisk/issues/3413

or a number of others mentioned here:

https://github.com/topjohnwu/Magisk/issues

Could keep an eye on these, or try Patching Images method (flash w/ Fastboot) suggested just to check possibility... PW

---------- Post added at 02:56 PM ---------- Previous post was at 02:29 PM ----------

Great!... You could have run Terminal App on device too. ;)

Think you'll be spoofing Nexus 5 with default value unless this has been changed... You will likely get better device/OEM specific functionality manually choosing Pixel 4a, etc as mentioned...

Think you'll simply have to clear Google Play Store data for 'device is certified', assuming ctsProfile is now passing. PW
[Magisk] tramp20:
Thank you, so I am not alone :(

Can I flash Magisk-v21.1.zip without TWRP or MM?
[Magisk] zgfg:
Why simple, if you could do it complicated way?

There is Terminal, Termux (I like NetHunter Terminal) apps on Playstore
[Magisk] pndwal:
Yes, since you're rooted already you could give apps like EX Kernel Manager

https://xdaforums.com/general/paid-software/app-ex-kernel-manager-t3560850/post71130776

or Franco Kernel Manager

https://medium.com/@franciscofranco/faq-for-fk-kernel-manager-android-app-f5e7da0aad18

a go.*

Here's an article on relevant features/usage:

https://android.gadgethacks.com/how-to/flash-zips-without-twrp-or-any-custom-recovery-0193246/

Think you should try official alternative method first though...

*Nb. I've neither used, nor am I endorsing these methods... But I would be happy to hear any reports from intrepid users...

Nb2: You can also boot-only to TWRP (without flashing, even with stock recovery on device) by running 'fastboot boot TWRP.img' with phone in fastboot mode and TWRP.img in PC fastboot folder. Some have successfully flashed images this way even with incompatible TWRP (eg flashed on Android 11) booted-only after same failed if flashed to device itself. PW
[Magisk] zgfg:
You can

You can disk-dump by adb your current boot or recovery image (where you install Magisk to your phone).

Then (re) patch on another (rooted or not) phone, finally flash back by Fastboot
[Magisk] J.Michael:
I think the answer is "No, you cannot flash Magisk-v21.1.zip without TWRP or MM." If you can't use TWRP, you can't use the magic Magisk.zip. You have to patch a boot image and flash it. If you have a working fastboot, that's probably how you flash magisk_patched.img.
[Magisk] Tom_Scott:
Hello,

today (15.11.2020) I got an information about a new Update of MAGISK-Manager. But unfortuately after installation the Magisk-Manager would not startup anymore. The screen is flashing sometimes and then the Magisk-Manager is stopping. Anyway the hiding mechanism is still working. Also the root access. But I cannot go into the manager anymore. Does anybody other facing this issue?

Modules I have installed:

I have installed two modules for Magisk more than one year ago: "Magisk Hide Props Config" and "Viper4Android".

Recovery tries:

Also I have tried to to fix this issue by installing an earlier MAGISK-Manager version from March 2020 with help of Titanium Backup- But it wont help as the screen flashing is still there and the Magisk-Manager stops execution.

Have a nice week

Tom
[Magisk] zgfg:
Maybe your previous version of Magisk Manager was hidden/renamed/repackaged?

In that case uninstall both the old hidden/repackaged Manager and the new one, and install again
[Magisk] BillGoss:
I find that just uninstalling the "extra" Magisk Manager is sufficient. After doing that the hidden Manager works fine.
[Magisk] zgfg:
Ok, but the point is that Manager has a bug, it does not update correctly if old one was hidden (probably in case of updating from 7.5 1 to 8.0.x or so), but they forget about the old hidden one and report a problem that newly installed version does not work

Somebody with the problem should have report to the Github
[Magisk] Tom_Scott:
I find only one Manager on my phone. So I can only uninstall once.

Where can I find the new apk of the Manager?

Will try to go your way.

So long....

Tom
[Magisk] s1m0nw:
I have rooted my samsung tab s6 lite using magisk keeping stock rom in place. Used magiskhide to hide root and pass cts etc.

Used magiskhide and enabled disneyplus and it wont play videos. Also I cant for the life of me get netflix to install and load properly this app also doesnt appear in play store.

After reading through forum I checked the play protect to see if its says certified, which it does.

I jave root an older tablet before and it was a piece of cake, but theres obviously been updates between then to the newer devices.

Main reason for me keep stock root is so that I can mass transfer my daughters apps from sdcard to extsdcard.

Anyone have any suggestions?
[Magisk] BillGoss:
https://github.com/topjohnwu/Magisk
[Magisk] snke:
Thanks, but i think i will stay with superSU waiting for Chainfire ?? I'm not able to uninstall phhsuperuser
[Magisk] Ch3mist:
Was reading the threads. What i gather is i dont need magisk anymore i can just flash pph's root+hidesu and i can play pokemon again while still rooted ?

can i remove magisk and just flash hidesu ?
[Magisk] teddy0209:
You sure can, if you don't use any magisk mod...
[Magisk] ameel:
You are so many steps ahead you don't even know the difference between superuser and supersu, hidesu and suhide. The other guy is right. Suhide with supersu doesn't pass safetynet, but hidesu with superuser works and passes safetynet
[Magisk] Ch3mist:
So i can use magisk unstaller to remove magisk and just flash the hidesu.zip ?
[Magisk] teddy0209:
Maybe... I don't use uninstallers, I just delete the magisk.img and restore my boot.img...
[Magisk] Ch3mist:
Never tried deleting the .img before, Possible you can tell me the steps ?
[Magisk] teddy0209:
Using file manager in custom recovery... It is in /data
[Magisk] rhyzan:
Heya [MENTION=4470081]topjohnwu[/MENTION]. Great work on magisk. Some kinks yep. But still, solid work.

But I do need some help in Magisk 7. I have a G-900L running on CM13. There's not much roms that could cater to 900L so I used a modified boot.img that could allow my device to boot 900F roms.

So the first time I flashed magisk 7, phh superuser and 86.6 xposed with usual latest nightly, gapps. Cleared out the caches and also system partition (because I moved out from SuperSU.) So it was successful. Great ****.

Then I saw the systemless version of the audio mod I used (Divinebeats 8) so I tried to flash that AFTER the initial boot of the device. Cleared caches. Flashed the thing. Then this happened.

So the S5 bootloader screen came up. Usual stuff but it took a bit longer. Then the boot screen came up. Took a bit slower too. Then it either bootloops for a while then force reboots or goes to the optimization screen and force reboot. I couldn't get the liveboot logs or any logs.

I tried flashing it again. Removed the systemless audio mod. Tried flashing magisk 7, phh and xposed only but to no avail. Gonna do a clean install soon after I made a nandroid backup. Attached on this post is the modified boot image I used,in case you need to take a look at it.
[Magisk] lukazaz:
Stupid question but, what happened to the enable/disable root switch? Magiskbstoped working (6?) So I updated to 7 but for the love of corn candy I just can't find the root disable button :|
[Magisk] iamelton:
apart from "/data/magisk.img", also remove "/data/busybox/", "/data/magisk/", "/data/.magisk", and "/data/stock_boot.img" which are all files created by the magisk package..

"/data/.magisk" does not exist in my installation of Magisk v7, but i found it in the magisk uninstaller script..

"/data/stock_boot.img" seems to be extracted from my systemless SuperSU installation which backs up the stock boot image as "/data/stock_boot_*.img.gz"..
[Magisk] gqukyo:
Should search before you ask, been answered quite a few times. The switch had been removed for the time being as it didn't work anymore.
[Magisk] lukazaz:
So for the moment and for an indoor option should I just remove root files? And unroot? Since I need it for Android pay I will just unroot for the time being hopefully the switch will work again in the near future
[Magisk] gqukyo:
Unfortunately yes, you'll have to unroot unless you want to try the supersu hidesu zip mentioned a few pages back.
[Magisk] Ch3mist:
Unfortunately after i remove magisk, and flashed the hidesu.zip i was good to go until i restart the phone and was softbricked. Cant mount system in twrp can only mount sd card so i had to resort to stock rom cause it wouldnt allow me to flash the bootloader in odin " secure check fail bootloader " hopefully someone can help. Cant install no roms since it wouldnt mount system.. I'm using s7 edge was using the superman rom before the softbrick
[Magisk] Rhoban:
Chainfire himself stated the his suhide may not be updated anymore, because it is no long technically interesting to him.
[Magisk] ibrokemypie:
that w was quick, cant say i didnt expect it though

somewhat worries about the future though if phh is the only one left on it right now...
[Magisk] cthulhu1987:
Did anyone try the new method on a custom ROM such as, say, CyanogenMod, Slimrom or similar?
[Magisk] royaLred:
You mean this? http://xdaforums.com/showthread.php?p=69010176

works for me on Darkwolf.

Gesendet von meinem SM-G935F mit Tapatalk
[Magisk] cthulhu1987:
Thx, gonna try and post the results here.
[Magisk] pndwal:
I'd clear data for Playstore anyway, toggle hide off and on again in Manager settings, if you have Netflix / Disney plus as system apps include these in Manager Hide list, reboot, uninstall all updates and clear data for these, reboot and check if appear in playstore, if not, don't forget to add to hide list when you can install them... for starters... :D PW
[Magisk] ipdev:
Bit OT..

I do not know about Disney.

Netflix does not need to be hidden or Play Certified. ;)

It is some F'd thing that Google and Netflix have never address properly.

Who knows maybe it's a lovers' quarrel between them. ¯\_(ツ)_/¯

PlayStore will show and install Netflix on Non certified devices.

Netflix offers apk download links.

Along with instructions on how to disable auto-update in PlayStore.

Once installed PlayStore will take over updating Netflix.

It is something on the device/rom/settings side that triggers the initial reject from PlayStore.

Certification and/or root do not seem to make a difference currently.

Cheers. :cowboy:
[Magisk] pndwal:
Interesting insights... :good:

I knew it didn't require hiding root in past, and of reports it showed/ran without certification, but looked like something might have changed, so included these possibilities to cover some extra bases...

So fix is still unclear? Think uninstall all updates and clear data for these may help? Or something else? PW
[Magisk] s1m0nw:
Small update, managed to get netflix up and running was quite easy guess I just need to take a step back and try again. With it being a system app I uninstalled all updates went to apk mirror downloaded and installed there latest version for tablet and viola we have a working netflix.

So thats netflix and prime now working. Now I have to concentrate on getting disneyplus to work.

Anyone any suggestions on how to get disney plus to work? Is there a file to install on magisk that I have missed.

Cheers
[Magisk] Didgeridoohan:
I don't think Disney+ looks for Magisk... At least I have no issues on my device and have not had to add Disney+ to MagiskHide, it just worked out of the box.
[Magisk] Legion666:
with latest magisk and manager the apps that i hide using magisk hide are crashing. i have hidden the magisk manager. when i use magisk hide for pubg, gpay, phonepe, my jio they are all crashing. when i remove them from magisk hide they work but detect root. can someone help me please.
[Magisk] s1m0nw:
Mmm, i will try again. Netflix is now shutting down. Is there any way to remove the system app and install standard apk?

Or would I be better flashing a rom.
[Magisk] zgfg:
https://xdaforums.com/mi-9t/how-to/magisk-module-systemless-debloater-t4180083
[Magisk] Tom_Scott:
After deinstall all MAGISK managers and reinstall the newest one the crash was gone.

One thing is left: I found out that I cannot download the magisk-manager.apk from GitHub with an Android mobile device. It is stuck while downloading. But with a common Windows PC downloading works. Maybe there is a safety mechanism that protect downloading apk's or something else. Never mind...

Ciao

Tom
[Magisk] zgfg:
You must have only one Manager, not several of them installed

If you use e.g. browser, you must allow Storage permission to be able to save the download.

Check also that your adblocker, firewall or something does not block github

Also, your browser may not download to /Download folder, but you must use Downloads app to access the downloaded file

In short, I can download (and install) the Manager apk with no problem, from the Github and directly on my Android phome
[Magisk] Racer-ex:
Replacing boot _a and boot_b without rebooting in between kills wifi

I'm rooting a Qualcomm SDM-630 phone that has boot_a and boot_b configuration. Device is running Android 8.1 as packaged by ATT. There is no TWRP available for this unit. I follow the general instructions to generate magisk_patched.img no problem. However, when I use Qualcomm "Emergency DownLoad", (EDL) and replace boot_a with magisk_patched, reboot the device into Android, then boot back into EDL and replace boot_b with magisk_patched and reboot into Android, it works great and I get root. However, (on a fresh install) if I replace boot_a with magisk_patched, then replace boot_b with magisk_patched without a reboot in between, my wifi is totally gone afterwards even though I have root using this method. Only a stock reinstall of Android OS will get wifi back. What is up with this? How can I get wifi back? It seems as if I should be able to swap boot_a and boot_b with magisk patched without a reboot in between with no problems. This is not the case, only issue seems to be loss of wifi. Toggling the wifi switch in Settings>Network&Internet> does nothing, it resets back to "Off" after 2 or 3 seconds.

Anyone else aware of this issue? Thanks in advance.
[Magisk] s1m0nw:
Manage to uninstall system bound netflix and installed netflix.apk. Now it just crashes.

Disneyplus loads but comes up with error code 39.

Anymore suggestions?

I have have the libcrypto active and hidden dplus and netflix and unhide. Still no joy.
[Magisk] RandomPooka:
Some hosting services won't let you download from mobile very easily. You might try tapping the 3 dot menu on the upper right and selecting "Desktop version" to trick it into thinking you're on a PC. Works for me every time.
[Magisk] Alxoom33:
Nice to see that you are still around. I remember you from my N6 days, back in the 20teens...
[Magisk] RandomPooka:
I think I might still have that device lying around somewhere...

I've mostly been lurking around, and waiting for sometime who knows a metric butt-ton more than myself to figure out A11 decryption for TWRP.
[Magisk] zgfg:
It's systemless debloating, you can always re-enable back.

Maybe you needed to try:

- uninstall Netflix updates (Settings, Apps)

- systemless debloat and reboot

- delete Netflix data remnants from /data/data (you can find and delete manually but you can get help by MiXPlorer, three dots menu, Tools, App remnants)

- then install Netflix
[Magisk] s1m0nw:
Just tried this. Theres no remenants of netflix left installed netflix and just the same.
[Magisk] zgfg:
Check if Netflix maybe also remembers something to Internal memory, Android/data folder (or somewhere else)

On my MIUI, there was some Netflix_activation preinstalled as system app, if you have anything like that (try to debloat as well), it could cause to require also the stock Netflix apk

Sorry, no better idea, not using Netflix
[Magisk] Alxoom33:
Ha, my N6 is long gone. Still have my Taimen and TWRP decrypts just fine for me. What device do you have? TWRP decryption is very device dependent. However if you have an A/B device you can't have TWRP and Magisk co-existing in A11 Boot partition. You need to root with Magisk and fastboot boot up twrp.img, as needed.
[Magisk] mayur.3.92:
Magisk installation goes fine in TWRP however post reboot magisk says not installed.

Any suggestions on fixing this?

OS : LOS18, Device OP5.
[Magisk] Nizar3003:
so even with magisk hide, my pubg still doesnt start. Any idea about this?

Should i using magisk hide module and bussybox?
[Magisk] Pundy:
I have the same problem with my OP6@LOS17.1.

I guess this is a LOS problem cuz they included a magisk addon.
[Magisk] KtownJeff:
Use a root explorer and see if u have sbin directory at /....if not add it and it will be installed but MM may not say it is...I'm flashing modules with smart pack kernel mgr
[Magisk] Soumy1234:
Try installing BusyBox. I also had to hide Magisk Manager, install Edxposed and SudoHide, and hide the repackaged Magisk Manager from PUBG.
[Magisk] tramp20:
The same problem here with Lineage 17.1 and AICP 15.0 (both Android 10).

Magisk 20.4 without any problem, but Magisk 21.1 (with all canaries before) behaves exact as you described it. Neither Magisk nor Manager are installed :(
[Magisk] 1234wtrs1:
I used to be able to pass basicintegrity but after the latest magisk app update, I'm failing it. Any fixes?
[Magisk] Didgeridoohan:
Make sure that MagiskHide is enabled and working.
[Magisk] 1234wtrs1:
It is. I haven't changed any settings. Everything was working fine.. A update notification for magisk showed up and i allowed the install but after that, I'm failing safetynet
[Magisk] Didgeridoohan:
Maybe it wasn't apparent, but that was a link to tips on how to possibly fix your issue (#1 tip if MagiskHide is enabled: toggle it off and on again) and how to test that MagiskHide is actually working.
[Magisk] 1234wtrs1:
I did check that out but still the same :( I don't know how it stopped working all of a sudden
[Magisk] Didgeridoohan:
Neither do we. Keep reading that guide and maybe you'll find something that fits your setup (there are quite a few things that can cause SafetyNet to fail).
[Magisk] pndwal:
One likely candidate: Problem Magisk Modules (incl. EdXposed) trip basicIntegrity:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469 PW
[Magisk] OreganoPlanter:
Magisk and Verizon Samsung S7?

Help. I've been all over the interwebs and I'm starting to lose track. I'm trying to root a Verzion Samsung S7, Model SM-G930V with G930VVRU8CRJ3 bootloader with the Qualcomm MSM8996 CPU. Running Android 8.0.0 with Security patch Oct 01, 2018.

I've seen conflicting info about Magisk being able to root it. Apparently the bootloader is still locked.

Can one of you XDA Gods (heck, I'll take a demi-god or even a hero type) please confirm if this can be done or not? Thanks!
[Magisk] pndwal:
Should be quite do-able w/ unlocked bootloader. Highly unlikely if locked, at least on any modern device... Also, you will most likely need to sacrifice Knox fuse & security partition / 'Enterprise' functionality.

Guess you'll need to search device forums for method... Not sure if Version branding poses any difficulty.

Also, see special considerations for Samsung devices in official Magisk Installation Instruction; linked from here:

https://github.com/topjohnwu/Magisk PW

PS, I'm a mere mortal, not at all heroic either... For Divine assistance you may need to pray... hard...

PPS, Fresh oregano has phytonutrients, which fight infections such as staph. Other uses include treating menstrual cramps, rheumatoid arthritis, urinary tract disorders including urinary tract infections (UTIs), headaches, and heart conditions. The oil of oregano is taken by mouth for intestinal parasites, allergies, sinus pain, arthritis, cold and flu, swine flu, earaches, and fatigue... but I guess you know this...
[Magisk] K4KKBNO1:
Is there any fix for the safetynet failing problem??
[Magisk] xunholyx:
You do realize this website has a search function in the threads, right? This has been discussed here often lately.

Safetynet is failing with HARDWARE attestation I assume? Use this module to force BASIC attestation.