yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Nb. The solution suggested is a brand new feature in MagiskHide Props Config to spoof basic SafetyNet attestation in devices newly detected as supporting hardware backed attestation (working for now, but presumably only during a Google-testing-phase).

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

Nb 2. To ensure hardware backed attestation detection is in fact the cause of your ctsProfile failure, you can see the attestation type used by installing Canary Magisk Manager and running SafetyNet check. PW
[Magisk] oppala07:
as long as i can see, the only custom rom that work with A6 SM-T280 don't play videos or sounds, and is "still" in early development days. so this is a no no.
[Magisk] GuyInDogSuit:
Ah, yeah, I'm on the latest Canary build. That could be why.
[Magisk] drezz2:
yeah that's why i don't understand what's happen
[Magisk] Maxwell Miller:
Greetings...I have a doubt...I already installed Magisk Manager on my cellphone... but when I run the app it ask me to install magisk's latest version wich is 20.4 I believe ..how can I solve this problem... because I already downloaded the zip but it ask me to parch some sort of image or file that I can't find
[Magisk] Homeboy76:
What Cellphone?
[Magisk] casouzaj:
Go to Settings > Apps [& Notifications], browse down to find Magisk Manager (or whatever name you gave it when (if) you renamed it), select 'Storage' and see where it is resides. If not in the internal storage, move it to that location.
[Magisk] Didgeridoohan:
The zip is for flashing through a custom recovery (TWRP), not from the Manager (unless you're already rooted). If you're not rooted and have no custom recovery you have to install by patching your device's boot image and flashing that manually.

You might want to take a look at the installation instructions before proceeding:

https://topjohnwu.github.io/Magisk/install.html
[Magisk] HippoMan:
Does anyone know whether the latest Canary offers INSTALL->INSTALL->Install to inactive slot (After OTA) after installing the TWRP A/B Retention Script after an OS OTA upgrade?

I would like to use this method to install an OTA. This always worked fine for me in the past with the non-Canary Magisk Manager, but I never did it with Canary before, and I want to make sure that I can still rely on this procedure.

Thank you very much.

.​
[Magisk] RandomPooka:
Maybe just try it now without doing an upgrade to see if that option is present? That would be quite easy.
[Magisk] HippoMan:
I don't want to try something which might hose my device ... even this scenario without an upgrade. However, if after a reasonable amount of time no one offers any feedback, I will then probably give in and try it with my fingers crossed. But if anyone has already gotten that to work under Canary, that will give me more confidence.

.​
[Magisk] RandomPooka:
Nobody is going to offer you an answer to a question you could have answered by looking to see if that option exists in the place you clearly already know it will be if it exists.
[Magisk] HippoMan:
The "Install to inactive slot (After OTA)" does not show up when I select "INSTALL" on the main page of Canary. However, it might appear after I install "TWRP A/B Retention Script". But I have never installed that retention script under Canary, and I don't know whether installing it might cause some sort of problem under Canary.

Furthermore, even if that option appears after installing the retention script, there might be some sort of issues with Canary which could cause problems when actually using that OTA method. After all, there have been other issues with Canary builds in the past, and that's why they are called "Canary".

It's therefore perfectly reasonable to ask if anyone has been successful with this procedure under the latest Canary.

.​
[Magisk] JudgeDread11:
I am using dial boot on my OnePlus 7 and therefore can't use the retention script.

But before I started using dial boot I never had problems with it while on canary.

That said, the option "install to inactive slot" should be there even before installing the retention script. (First select the install options, and click next. It should be there) If it's not, it's not likely going to show up after the script either.

Lastly: Make backups.

If you worry about running into problems you shouldn't be rooting/flashing anything on your device. There is always a chance something goes wrong.

And every version of canary might have their own set of bugs which could all be environment specific.

Always have backups or be prepared to start from scratch.
[Magisk] HippoMan:
Thank you for taking the time to respond to my queries.

Yes, I always take backups, and I know that using Canary can come with risks, and I am always prepared for restoration work. It's just that I wanted to know whether anyone had been successful using the retention script under Canary. A bricking-followed-by-restore can be time consuming, and I don't even want to *try* that retention-script procedure if no one else has ever successfully utilized it under the latest Canary ... and in that case, I'll do the OS upgrade differently. That was the sole purpose of my question.

Also, thank you for pointing out about using "next". In the non-Canary version, we have this:

INSTALL->INSTALL->Install to inactive slot (After OTA)

... while in the Canary version, I now see that we have this:

INSTALL->Next->Install to inactive slot (After OTA)

I had been looking for that second "INSTALL" in Canary, and I overlooked "Next".

.​
[Magisk] hfam:
Pixel 4a and Magisk

Hello all!

I've got a Pixel 2 that I love, been using Magisk since 14 I think? I see the 4a is available for pre-order.

Does anyone have any knowledge of whether or not we will still be able to unlock bootloader? I presume if one buys it from Google (I did for my Pixel 2) we can still unlock.

The real issue is whether or not I can still use Magisk to gain root. I just use root and block a few apps just in case they detect root, but don't use modules. Having root is fine with me.

I know it's in prerelease but many of you folks seem to have an amazing depth of knowledge industry wide so I figured it can't hurt to ask as I'm trying to decide whether or not to grab a P4a and retire my P2.

Lastly, on my P2 for monthly updates I don't take OTA and instead use the full image, remove "-w" from flash-all, patch boot.img method. I do not have or use TWRP. Hoping that this would still be possible on the P4a. I believe things have changed a bit since the P2 with regard to how this is done but hoping someone can confirm or deny based on the P4. I'm assuming the P4a is primary a change of processor, camera, and 5g added from the P4.

Thanks for any and all insights. I read this thread every few days to keep up but my P2 feels ancient and irrelevant to any current data, methods and hardware and I'm not versed in the P4 platform.

hfam
[Magisk] pndwal:
I have zero experience with Pixels, but the following may help / look positive:

https://www.droidwin.com/root-pixel-4a/

https://www.xda-developers.com/google-pixel-4-root-magisk/amp/ PW
[Magisk] knpk13:
I recently made a similar switch from a OnePlus 3T to a OnePlus 7T Pro.

I'd expect the 4A to have an unlockable bootloader if you get it from Google, haven't seen any reports thar would indicate otherwise.

Magisk is already working on Android 11 Beta, so as long as you can unlock the bootloader and patch the image you'll get root. You said you don't use TWRP (it doesn't full support android 10's dynamic partitions yet) but I'd still recommend reading up on dynamic partitions (and fastbootd to manage them) for newer devices, there's some news articles on XDA (and source.android.com) about it too. They're easy to find, but I can send you links if you want. Other than that, based on your description, you should be fine with any new device. I'd recommend going to your device forum for device specific questions though (when it's opened).

There's an easier way to update newer A/B devices with an OTA while keeping magisk (you can flash magisk to the inactive slot after an OTA, which happens while the system is booted, no need to go to recovery/bootloader to update anymore). I'd recommend that over the method you use, which is what I used to do for older A-only devices.

Magisk is not guaranteed to hide root soon, because of Google making server side changes and using hardware attestation (search the thread for "safetynet" to find out more) so I'd keep that in mind as well. Safetynet currently passed for me on all my devices but that could change for the newer devices that use hardware attestation.
[Magisk] hfam:
Ahh, thanks for the links, it indeed seems all is well with regard to getting root on the 4a then! Much appreciated!!

---------- Post added at 09:18 AM ---------- Previous post was at 09:00 AM ----------

Excellent info and suggestions, thanks! I definitely will go research up on dynamic partitions and fastbootd, sounds like I could have been using that method on my P2 as it has A/B. I don't mind the current method I use as I'm super comfortable with it, but as with all things over time, gotta change with the times so appreciate the advice! If you have a link or links that you feel address the subject matter well I always appreciate the assist and am grateful for any links you care to share, but I will go looking as well. Really want to get as solid on the P4a methods and understand it all as well as I understand my P2.

The attestation SN issue I suspect is in stone and maybe some clever bastard will come up with a means to defeat it for root hiding purposes anyhow, but yeah, were gonna have to deal with the fallout on that at some point. For now the ol P2 is still passing....for now.... :)

I do believe going to go place my preeorder based on your feedbacks, gentlemen! I really appreciate the quick and super helpful replies, and again if you have a link or 2 you know address that info well, I will put it to good use!

Thanks again fellas and be well,

hfam

---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------

Excellent info and suggestions, thanks! I definitely will go research up on dynamic partitions and fastbootd, sounds like I could have been using that method on my P2 as it has A/B. I don't mind the current method I use as I'm super comfortable with it, but as with all things over time, gotta change with the times so appreciate the advice! If you have a link or links that you feel address the subject matter well I always appreciate the assist and am grateful for any links you care to share, but I will go looking as well. Really want to get as solid on the P4a methods and understand it all as well as I understand my P2.

The attestation SN issue I suspect is in stone and maybe some clever bastard will come up with a means to defeat it for root hiding purposes anyhow, but yeah, were gonna have to deal with the fallout on that at some point. For now the ol P2 is still passing....for now.... :)

I do believe going to go place my preeorder based on your feedbacks, gentlemen! I really appreciate the quick and super helpful replies, and again if you have a link or 2 you know address that info well, I will put it to good use!

Thanks again fellas and be well,

hfam
[Magisk] Didgeridoohan:
Modules in repo get audited before approval. For a while there was a small group of us that helped [MENTION=4470081]topjohnwu[/MENTION] with that, but now he does it himself.

There's nothing to stop someone to change the module once approved though... Luckily most modules are plain open source so you can check them yourself before installing.
[Magisk] pndwal:
Just some food for thought here...

COMMENTS FROM OP

John Wu

Aug 3

This marks the end of the recent short burst of libsu development, will redirect my free time now back to Magisk

(libsu- An Android library providing a complete solution for apps using root permissions.)

John Wu

Aug 5

iPhone or Pixel, it's not that hard ?

The argument here is: iPhones and Pixels are the only phones I know that are completely "clean" out of the box. When you buy an iPhone, everything on it by default is from Apple; for Pixel, it's all Google. No ads, no "bundles", no office suites, no dumb ass "optimizers".

And yes, both iPhone and Pixels are relatively more expensive, but what you are buying is quality engineering. I'm not saying they are perfect, but relatively speaking I only really trust phones straight from Apple and Google.

"Google has already discontinued the Pixel 4 and 4 XL"

theverge.com

John Wu

Aug 6

Awesome, my distaste towards Android is growing day by day. Thanks Google...

John Wu

Aug 7

But seriously speaking, there's still Pixel 4a, a good device, just not a flagship

"Count down initiated

Beta 3 marks the #Android 11 final beta update! See all that’s new as we get closer to the official release!"

Android Developers

John Wu

Aug 7

Guess I have to speed up polishing Magisk for a proper stable release before Android 11 is out...

https://mobile.twitter.com/topjohnwu/with_replies

So, new polished Magisk Stable release coming soon?... Seems an age since 23 March! PW
[Magisk] knpk13:
Can't really offer any insights on choosing a device to buy, that's your decision. If you're mostly on stock and magisk, the A/B dynamic partitions/fastbootd stuff is just nice to know to have a simplified understanding of how it works under the hood. You're unlikely to have to select slots manually or use fastbootd unless you're flashing custom ROMs; you can just use magisk manager to update and patch stock. These are the links I can think of off the top of my mind. I'm sure the 4a forums will have specific guides when they're out, should be similar to the regular pixel 4.

https://www.xda-developers.com/android-q-dynamic-system-updates-project-treble/

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

https://source.android.com/devices/bootloader/fastbootd

https://source.android.com/devices/tech/ota/dynamic_partitions

https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

Topjohnwu has switched to Twitter for updates; this is one of the relevant threads (note the dialogue between phhusson and Shawn wilden) on safetynet

https://twitter.com/topjohnwu/status/1237662699233792000?s=19
[Magisk] Rokcy98:
Hi guys.

I have a S8 with LOS 17.1 on it. This morning, at a glance, both basic integrity and cts became false.

I've already changed fingerprint with an s8'one and a pixel 4's, tried hardware off module, cleared services cache and disabled play protect, but nothing. I've magisk hide enabled, safetynet has been passed for almost a year without any problem, until now.

Do you think I can try something else?

Thanks in advance for the help

P.S. I actually have July security patch
[Magisk] pndwal:
Interesting evalType shows N/A! ... Anyone else seen that?

Please confirm MagiskHide is toggled on in Manager settings, and try toggling off then on again. Also, please say which modules you have installed. PW
[Magisk] Rokcy98:
Yeah, I couldn't find any other case of eval N/A... Btw modules are busybox, 1controller, v4a, liboemcrypto, magisk hide props config, Google product sans and Samsung uhd camera fix, so not weird or experimental modules
[Magisk] pndwal:
Could try booting after disabling all modules or enabling core-only mode (Nb. You'll need manager v285 or earlier) to test if any module is causing basicIntegrity fail. (Nb. You need to sort this in order to pass ctsProfile). PW
[Magisk] IzaacJ:
The bootloader isn't locked OOTB, and when I've manually unpacked the boot.img it's been gzipped.
[Magisk] KaMyKaSii:
I understand. When you say "brick" mean that stuck in bootanimation or not even pass logo?
[Magisk] xd4d3v:
Updated to v7, uninstalled and flashed magisk with no problems.

however, the Manager v2 automatically closes when i try to open it?

already cleared data, etc.. anyone else having the same issue?
[Magisk] zzzhead:
Would like to report, systemless ViPER4Android breaks xposed one tap video download module
[Magisk] chudy_85:
Yes if you use Supersu by Chainfire.

Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
[Magisk] teddy0209:
If you are using phh superuser, you have to set selinux to permissive...
[Magisk] adam_99:
Where can I find it?

I used to do it with Magisk Manager but it's gone now.
[Magisk] teddy0209:
Just search how to set it to permissive... there are apps out there than can set it.
[Magisk] adam_99:
After short search on google, couldn't find any.

Do you know what's the procedure to revert to Magisk V6?
[Magisk] teddy0209:
Did you try searching for selinux mode changer?... Restore boot.img, remove magisk.img in /data.... then flash v6...
[Magisk] adam_99:
Found it.

I'll try it.

Thanks!

Update:

The app doesn't work.

It prompts for no root.
[Magisk] IzaacJ:
Running df /tmp in the TWRP terminal shows almost 246mb free, so I don't really understand how there can't be enough free space when the original boot.img that I flash is ~4mb :eek: However, in the log it seems like it is copying 400+mb :eek: Seems weird...
[Magisk] devilloki:
did not root,only flash v7, but magisk manager v2 FC
[Magisk] soder:
Oh, to bad. That one I've used, but the Viper I still havn't notices anything great with. =)

/Söder
[Magisk] teddy0209:
You have to root... and grant the manager root access...
[Magisk] westeight:
SafetyNet, Android Pay, Pokemon Go and Xposed all working with Magisk 7.

Just tested AP:
[Magisk] Tesla:
Magisk manager v2 FC after one use.

Have to clear app/data for it to start again.

1. Note 3 N9005 - Kernel and rom in sig.

2. Pogo works. :good:

3. No xposed installed yet.

4. Root works
[Magisk] putridfoetus:
FYI, this did not solve the problem of SystemUI fc'ing constantly. I think I found my problem, though. I was stupid and removed the REPLACE="" section from config.sh, so I think Magisk was doing its job too well and mounting a crippled system. logcat was full of missing libs and hw failures. Lesson learned.
[Magisk] dimm0k:
just wondering, do you have to reboot each time to enable/disable Xposed? also, are you using SuperSU or phh's root?
[Magisk] Rokcy98:
On the older magisk it says "response is invalid" even if i enable core only
[Magisk] MatthewOffical:
Hi!

I rooted my op 7t pro several times, but now I did a clean install with OOS 10.0.10 and tried to boot the patched image. After reboot I lost SIM connection and WiFi also. Is this a magisk related problem? I did everything the same what I did last time, so maybe there're some changes what magisk doesn't support yet.
[Magisk] Didgeridoohan:
In that case, see if anything from here applies:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
[Magisk] andrea0807:
Is Magisk beta compatible with Android 11? Or do I need magisk canary?

Inviato dal mio POCO F2 Pro utilizzando Tapatalk
[Magisk] noni2724:
i installed magisk on my a70s and now it shows only 32gb storage instead of 128gb. is there any way to fix it as i tried to find a way and it seems only way is to get twrp which i dont have. is there another way to do it?
[Magisk] pndwal:
Regarding initial Android 11 Beta versions (1 & 2):

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

Nb. Currently, Magisk Stable and Magisk Beta link to the same 20.4 version. You need later Canary.

Android 11 Beta 3 is now out too, and Official 11 is to arrive soon.

https://android-developers.googleblog.com/2020/08/android-11-final-beta-update.html?m=1

Some have also successfully rooted pixel devices on Beta 3 w/ Magisk Canary.

Seems John is expediting a new stable Magisk as Android 11 Beta 3 is to be the last, and Official 11 is imminent.

https://mobile.twitter.com/topjohnwu/status/1291433629726330880?cxt=HHwWgMCm7eeCjOwjAAAA PW
[Magisk] vinay19882:
I'm facing an issue I have installed latest Build 20.4 , uninstalled it using complete uninstall and also twrp but still root is detected by banking apps and various other apps now tell me what should I do . tried installing other previous builds but now magisk manager app is not opening and crashing continuously. Please help me in this

---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------

My device is one plus 2 RR os 6.0 build android 8

---------- Post added at 06:38 PM ---------- Previous post was at 06:38 PM ----------

My device is one plus 2 RR os 6.0 build android 8
[Magisk] pndwal:
You need Magisk and MagiskHide toggled on as a minimum to hide custom mods.

Many apps say root is detected even when unrooted. These are in fact detecting unlocked bootloader and/or other mods, and may simply say 'root detected' when 'modified', 'insecure' or 'un-trusted environment' is actually meant.

Your options are thus:

- restore full stock environment and relock bootloader, or

- restore Magisk, MagiskHide, and other spoofing solutions likely needed (configured MagiskHide Props Config, hiding/renaming Magisk manager, TWRP etc, hiding root from Google services and banking apps in Magisk manager, etc etc) to achieve full SafetyNet pass, Play store certified status and non-detection of mods in banking apps by their own custom means.

(Also, please edit your double post above. :good: ) PW
[Magisk] toolhas4degrees:
You need to pull the boot IMG from the firmware and patch it in magisk since you used an old boot IMG that was patched for a different firmware version.

Next time update by downloading the update. Don't reboot

Go to magisk and select install magisk then install to inactive slot let it do its thing then reboot
[Magisk] zgfg:
MM Canary 292 released (and Magisk 20420), I see two goodies:

1) It can now test SafetyNet without Magisk installed

2) Does no more crash on opening Modules if there is no connection

Btw, might be a bug related to (2) - cannot be sure since I currently have only Internet mobile with bad connection:

- Test (2) with Airplane on, put Airplane off, restart MM, it stays forever in Loading, not showing if Magisk is installed and if there is an update

- Settings/Apps, delete Data for MM, then it immediately loads correctly

Edit:

Hiding MM still does not work for me with Canary, and actually before I finish typing the new name and press Ok it already pops up that Hiding has failed
[Magisk] HippoMan:
I also installed the latest Canary, and I am noticing the same failure regarding hiding, as well.

.​
[Magisk] Alxoom33:
You need to go into settings and activate Magisk Hide. Then you will pass.
[Magisk] HippoMan:
MagiskHide is indeed enabled in my Settings. However, when trying to change the name of Magisk Manager, the behavior described above occurs, and the app cannot be renamed or repackaged.

This occurs both with the latest Canary (292) and the previous Canary (291).

.​
[Magisk] stathis95194:
I seem to recall someone mentioning that if you disable Google Play Protect from play store settings it allows to hide MM. And you can reenable it afterwards
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] and [MENTION=1751428]HippoMan[/MENTION] The current workaround to hide the Canary Manager is to disable Play Protect and paste the name you want to give the app into the text box, don't type. Until the bug is fixed...
[Magisk] HippoMan:
Google Play Protect is disabled on my device, and sadly, I still am getting this problem with renaming/repacking Canary Magisk Manager.

Perhaps this is related to my device or OS. I'm running on a OnePlus 7Pro (GM1917), and I had this problem both with OOS 10.3.3 and 10.3.4 ... and in both cases, Google Play Protect has been disabled. I never ran Canary under any other OS version, so I don't know if I would have also had this problem under 10.3.2 or anything older.

And I have had no problem renaming/repackaging the non-Canary Magisk Manager under these OS's.

.​
[Magisk] zgfg:
Ok thanks, this workaround to paste the new name instead of typing it worked for me
[Magisk] HippoMan:
I tried that, and it only pasted a fraction of the name. I wanted to name it "HippoManager", and I copied that string.

When I pasted it, the the Magisk Manager did get renamed, but only to "HManager".

There seems to be some sort of race condition or other timing issue in the Canary UI when working with that particular dialog box.

.​