yashsingh1/xdaforums huggingface dataset:
[Magisk] DawoodSahi:
Still not passsing. Reboot automatically unchecks the apps in magiskhide menu/tab that I selected:

Google Play Services

Snapchat

SafetyNet Check apps.

Edit: it just bugs up everything as it did before. Root is lost (even phhsupersu app was gone) magiskhide tick is unticked automatically and rebooting doesn't fixes. Had to reflash everything from the beginning.
[Magisk] Abhi142:
Does it support android 7.1?
[Magisk] shantam3108:
Using it on 7.1 without any issues
[Magisk] cohiba90:
which is the file that i have to check to hide the SafetyNet?

I can not play Pokemon Go (magisk V9)

Thanks
[Magisk] Artim_96:
It's com.android.google.gms.unstable ... Or something like that
[Magisk] Didgeridoohan:
Hm... I have no such problems on my Nexus 6 - stock 7.0, November patch level with Franco Kernel r57. Magisk v9 and Magisk phh 266-2.

Maybe you've already provided this information earlier, but what's you device and rom?

And how do you reboot? Soft restart or a proper shutdown before powering up the device again? I noticed earlier (v6 I think) that Magisk Xposed would bug out if I did a soft reboot. [MENTION=4470081]topjohnwu[/MENTION] Could a soft reboot cause issues for certain parts of Magisk?
[Magisk] ghbuur:
just fyi. using superman rom on s7e, superkernel, magisk v9 with phh, no xposed. safetynet passes, except cts. pokemon works and more important "good for enterprise" from play store finally too (business mail app)!

even if it doesn't really matter, but what could cause failing "cts profile match"?
[Magisk] putridfoetus:
Magiskhide on Nexus 6

Question about magiskhide:

Nexus 6

Magisk v9

phh su 266-2

When I check the box to enable magiskhide and reboot, the entire magisk partition is unmounted by magiskhide (log attached). Is this expected behavior, or a peculiarity of my device?

Since the entire partition gets unmounted, there is no root, so have to mount magisk from recovery to disable magiskhide. Seems wrong to me...
[Magisk] Didgeridoohan:
See my post just above: http://xdaforums.com/showpost.php?p=69628346&postcount=5652

How do you reboot?
[Magisk] DawoodSahi:
I've a Xperia Z2 D6503, running on stock MM, custom advanced stock kernel, magisk v9 and magisk phh 266-2

I do proper reboot and I've also tried doing soft reboot. Same problem.

I've pretty much the same problem. Root is lost and for me, I just reflashed everything. Didn't know I could just somehow mount magisk from recovery and disable magiskhide
[Magisk] Abhi142:
What is the procedure? Plz help me
[Magisk] Didgeridoohan:
So much for that theory... Bummer. Might be a device specific issue then. You could add it as an issue on GitHub: https://github.com/topjohnwu/Magisk/issues

---------- Post added at 10:32 ---------- Previous post was at 10:29 ----------

Have you tried the installation instructions in the official anouncement thread?
[Magisk] putridfoetus:
I do full reboot. Also on stock 7.0 Nov patch, stock kernel.
[Magisk] HamsterHam:
Anyone got viper and Spotify to work together? Cheers.
[Magisk] dtective:
Did you manage to get Barclays app working with Xposed?
[Magisk] putridfoetus:
There's a mounting module in the modules thread you can flash in recovery to mount the magisk image and work with it. Just delete the ”enable” file in the module directory you want to disable.

http://xdaforums.com/attachment.php?attachmentid=3850581&d=1471875417
[Magisk] Didgeridoohan:
Interesting... So we have almost the same basic setup, with different results. What could be the culprit?

My (very) limited skill set around this is exhausted so hopefully someone with more knowledge can chime in. All I can contribute is that it is possible to get it working... :p
[Magisk] DawoodSahi:
Thank you for the help, although which file is it again that needs to be deleted and from which module directory specifically?
[Magisk] putridfoetus:
Can you post your magisk.log with magiskhide enabled? For me, the culprit seems to be the unmounting of all modules and magisk itself by magiskhide.

---------- Post added at 04:03 AM ---------- Previous post was at 04:02 AM ----------

/magisk/.core/magiskhide/enable
[Magisk] zgfg:
FBE is encryption for Data, to protect user (yes, Google's reasons, and actually I have no problem with, I like that)

SAR (System as Root), Super when you're flashing is read-only. Two independent and different things. Disabling FBE will not make System writable

Not only that System (/system, /system-ext, /product, /vendor, /apex and now /odm on A13 and /my_* partitions on the new One Plus devices) is read-only, but the partitions are 99% full (fill up to the last cluster). When OTA comes, Recovery resizes the System partitions (so-calked dynamic partitions), flashes them, makes them back read-only and even the System cannot write or even delete. Neither the root. That's why Magisk provides systemless rooting - on booting, it mounts the changes (like: AdAway writes to /data/adb/modules/hosts/system/etc/hosts file and Magisk mounts that to /etc/hosts). Or even Magic OverlayFS (if supported by ROM) - in that case you can even dynamically, upon booting, 'write' to System - but again, 'virtually', Magic OverlayFS dynamically mounts your changes to the System partitions

Check your /vendor/etc/fstab.* (Read with eg root granted MiXPlorer) to see if your System/Root is ro. Data is usually f2fs and System extm filesystems. And use df command in Terminal (su) to see how much the System is full. Even if not ro, there will be no space to add more the some KB or an MB

And I also like that - it ensures that you could not alter the System. You reboot without Magisk (or to TWRP) and System is unchanged. Otherwise you could have troubles with (partial) OTA. And it protects you to brick the System part

Dynamic partitions are also good, vendor does not need to reserve GBs for future OTA, writing to System and so. More space for Data and Internal memory

---

If custom Recovery cannot decrypt (for user 0), you see folders on Internal memory (like Download) but filenames are scrambled, like 'randomized'. Hence, if you see them correctly, decryption for user 0 was successful
[Magisk] pndwal:
Just as a clarification, RO filesystem ("ext4 dedup") is not an issue with legacy (first generation) SAR so RW worked in Android 9...

RO dynamic partitions (where vendors no longer have to worry about the individual sizes of partitions such as system, vendor, and product and instead the device allocates a super partition, and sub-partitions can be sized dynamically within it) were introduced with 2SI and shared blocks in Android 10... System images were then formatted as EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS...

www.twitter.com/topjohnwu/status/1170404631865778177

https://source.android.com/docs/core/architecture/partitions/system-as-root

🤠 PW
[Magisk] pndwal:
Both Magisk and TWRP load via init in ramdisk in a boot image. (Nb. boot.img, init_boot.img and recovery.img are all boot images.)

Recovery is always loaded via init in a recovery ramdisk, either in /boot, /init_boot or in /recovery partition...

Magisk is preferably loaded in a ramdisk in /boot or /init_boot partitions and this can be a boot ramdisk (where a seperate /recovery partition exists) or a recovery ramdisk (where no seperate /recovery partition exists, ie most A/B devices).

Where no ramdisk exists in /boot (Ramdisk=NO, only A-only legacy SAR Android 9 LV devices) Magisk always installs one if boot.img is patched/flashed and Magisk may work loaded in this ramdisk if bootloader supports ramdisk in boot...

All of the above are Boot mode Magisk installations.

Where no ramdisk exists in /boot (Ramdisk=No, only A-only legacy SAR Android 9 LV devices) and Magisk fails to load with magiskinit in a Magisk-added ramdisk due to (expected) lack of bootloader support, there is no alternative than to install Magisk in recovery ramdisk in /recovery partition.

This is a Recovery mode Magisk installation.

In all the cases where magiskinit is installed in a recovery ramdisk, if a custom recovery is used it can be seen that they must reside in both the same ramdisk (recovery init is patched by both Magisk and by custom recovery) and in the same partition... Further, this includes /boot or /init_boot partitions for most A/B devices as recovery ramdisk is generally in these partitions (the exception would be OnePlus (and other?) A/B devices sporting seperate /recovery_a and /recovery_b partitions) as well as /recovery partition for devices where no ramdisk exists in /boot and magiskinit must reside in recovery ramdisk in /recovery... Nb. In the latter case, custom recovery CANNOT be used to install or upgrade Magisk.

Hope this clarifies things. 🤠 PW
[Magisk] zgfg:
- What is your Android version?

- Do you have pin/password/pattern enabled as required to unlock when you boot into Android

- What is your TWRP version?

- Does TWRP ask you for pin when you boot to TWRP?

- If it asks you and when you enter your pin, does it accept and does it print that it successfully decrypted for user 0?

- Then, in TWRP, do you see correct names for the files on Internal memory, (eg, in Download folder) or they appear as scrambled?

- Use Advanced, File manager and try to copy or create a new file in TWRP, again eg in Download folder.

Or simultaneously click Vol- and Pow to take a screenshot in TWRP.

Or even easier, make backup of eg Boot partition in TWRP.

Then reboot to Android and find if the backup, screenshot or file you created was saved

---

Btw, when you go to Backup in TWRP, does it offer you to backup both Boot and Recovery or only Boot

And when you go to Reboot in TWRP, do you have an option to choose Slot a and Slot b, or no option for slots!
[Magisk] J.Michael:
What is "a boot image ported with TWRP"?

When @zgfg was asking questions about TWRP, it was to find out how well this TWRP works. He doesn't want you to install Magisk. You talk about TWRP running, so describe how much it runs, what options it provides.
[Magisk] HippoMan:
We could speculate and debate about Google's reasons for the way they keep "enhancing" the "security" with every newer Android release. But whatever the reasons, this is one of the causes for the usability of Android devices continuing to deteriorate over time for those of us who want to root and mod our devices.

But Google isn't the only one to blame here. Now that newer versions of Android offer more effective capabilities for detecting rooting and modding, many app developers have jumped onto the bandwagon and started using these detection utilities, and more and more apps are now being released which cripple themselves or even fully disable themselves on rooted and modded devices.

A lot of these apps are "banking" apps, but as time goes on, more and more apps that have nothing to do with finance are also crippling and disabling themselves on rooted and modded devices.

So far, it's been a losing battle for us rooters and modders to circumvent these OS and app "enhancements". Sadly, I am not optimistic about this trend ever reversing.
[Magisk] J.Michael:
If you have a problem mashing TWRP and Magisk into the same boot image, and you have no recovery image, then you should try keeping TWRP and Magisk separate.

You have some magic way of mashing TWRP into a boot image. Mash it into a boot image without trying to put Magisk into the same boot image. Then try booting that boot image with "fastboot boot TWRP-mashed-boot.img". The first question is Does it boot? If it boots, does TWRP seem at all functional.

Forget about Magisk. With TWRP in the boot image, how are you supposed to boot TWRP? If you are supposed to use some key combo to "boot to recovery", then someone else on here is going to have to speak to whether the "fastboot boot" option is even possible.
[Magisk] pndwal:
There are some guides for unofficial TWRP as well as root on your device per:

https://www.google.com/search?q=Tecno+Spark+8T+twrp

This one seems pretty good:

https://mobilewithdrivers.com/twrp/tecno-spark-8t-64gb-4gb-ram

From this it seems your device is not like most A/B devices, and this is probably the cause of your problems... It seems to have seperate recovery partitions,

/recovery_a and /recovery_b, like some OnePlus devices, so you'll need to flash as mentioned:

fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img

Then reboot directly to TWRP manually or using a fastboot command...

... So you will in fact have Magisk in /boot_a and/or /boot_b, and TWRP separately in /recovery_a and /recovery_b on your device...

.. Seems you may need to disable verity/verification for your device. Eg using fastboot command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

- Note that it may wipe your data

- Note that this may not be enough... May actually need 'No Verity Opt Encrypt Zip' recommended, but I'd try to simple fastboot method first...

You may find good advice in official TWRP.me installation instruction pages for devices with similar boot architecture, eg OnePlus 8T (A/B with separate recovery partitions)...

Applying Magisk root should be a simple matter with your device configuration after this...

Personally, I'd avoid using TWRP these days with stock ROMs as there are now numerous pitfalls and considerations... Generally these are better addressed when custom ROMs are used as the Devs must then ensure proper working configurations...

You'll find alternative methods for disabling Magisk modules (if you get bootloops etc) in official Magisk FAQs, and methods like safemode detection have been developed precisely because the existence of a custom recovery is no longer expected...

Hope this helps, PW
[Magisk] J.Michael:
From what you describe, the image you end up with for TWRP should be suitable for using without installing, but rather by running through fastboot.

Do you have fastboot?

Have you tried the command "fastboot boot TWRP-image"?

Don't be so concerned with flashing to both slots. Be more concerned with the image you start with when you "port" TWRP. If your device and ROM have a recovery partition, it seems likely that you should be using the original recovery image as part of the process of generating a TWRP-image -- you should not be using the boot image.
[Magisk] zgfg:
From all we see that TWRP is not compatible with the ROM/A11

So don't push further. If you are not developer with the source code, you will never make it work

It doesn't decrypt Internal memory (Storage) hence:

1) it cannot pick up an img or zip file from Storage (eg, Download folder) to flash

2) you cannot make backup of the partitions and save it to the Internal memory and later pick it up to restore

Maybe you didn't test but I'm pretty sure that your TWRP cannot read either Data partition:

- try either from Install (navigate back to /data) or from Advanced, File manager

- go to Data (/data) and check do you see folders, and if you go to the folders like /data/adb do you see magisk.db file there (assuming that you previously installed Magisk - ofc, not through TWRP) or navigate to /data/app then further to subfolders - eventually you have to see *.apk files

If not, then you will not be able to use that TWRP for:

3) going to /data/adb/modules/... to disable a module causing the bootloop (you mentioned that you want TWRP for that)

But I fear it's only a tip of the iceberg. From what you also described, your TWRP seems does not 'understand' the structure of partitions, etc.

Even if you circumvent the problems 1-3, ie that your TWRP is not compatible with FBE (eg, by sideloading a zip or img file you want to flash), the TWRP can screw up the System when flashing

Hence what do you want with?

Do you eventually want to brick your phone by using an incompatible TWRP (and then blame Google as it was their 'fault')?

---

Problem (1) could be circumvent by:

- using adb sideloading for providing (from PC, via USB), that zip or IMG file you want to flash

- or by putting that zip or img file to USB stick (or to micro SD card if your phone supports them); their filesystems are not encrypted and TWRP can read from them

Similarly (problem 2), TWRP can save the backup to USB stick (or micro SD card)... - but I doubt its backup would be of any use since the TWRP has the other problems

Problems 1-3 could be solved also by disabling FBE. First, I'm not familiar with the process and cannot advise you about (somebody else could) but again, you will need for that a reliable TWRP (to flash) and your TWRP isn't

Butt when you circumvent 1-3, it will just open you Pandora box to 'use' that incompatible TWRP to possibly brick the phone

Hence forget that TWRP. If there is no better custom recovery (I guess you searched) for your phone and ROM, live without

---

Btw, did you mention in som of the posts that you have MTK chipset?

Maybe you could use (I'm not familiar with for further details) MTK Flash tool (from PC) for some actions instead of the TWRP
[Magisk] pndwal:
For flashing Magisk, official instructions (not using custom recovery as it seems there's none available that are compatible with your android/ROM/device) should just work... No need to specify boot_a or boot_b... flash boot (per instructions) will flash to current slot...

Partition boot_b may be "hidden" as it's not in active slot... Only an OTA update or manual slot selection would swap to/activate that boot partition...

TJW got tired of issues with TWRP too, and only partly because Dees Troy and team are only human and update builds were not available even for already supported devices for some time after several major Android iterations came and went (Dees and other devs couldn't keep up / real life beckoned) while Magisk quickly adapted to the same, but also partly because flashing in custom recovery simply couldn't work for many 2018, 2019 1st gen SAR A-only devices (Ramdisk=No) anyway and a way of independently patching /recovery was required...

So the "equally or better good magisk" alternative is in-app patching and various kinds of download mode (fastboot, Odin etc) flashing... These methods completely remove the need for 3rd party custom support, development and updates from the Magisk installation equation, but the custom recovery installation method, while deprecated, "is maintained with minimum effort. YOU HAVE BEEN WARNED!", so is still available to use AYOR...

------​

I did notice that TWRP for Tecno Spark 8T Pro is more readily available, and this may well be a close match for porting, however there may be important considerations incl. ensuring that flashing partitions doesn't corrupt these...

Please be careful... It looks like a nice phone... 🙃 PW
[Magisk] zgfg:
Few short things, I'm busy

1) When testing unknown recoveries or boot images, don't flash them permanently to risk a brick:

fastboot flash ...

but just boot one-time to find first does it work safely:

- fastboot boot <img file>

2) To disable a module causing bootloop (or preventing you to properly boot and disable it through the Magisk app), use:

adb shell su -c touch /data/adb/modules/<GIVEN-MODULE'S-FOLDER-NAME>/disable

and reboot.

But first, once you install Magisk, make sure to enable su for adb (and allow your PC for adb, and test the adb drivers in PC), hence try something simple like:

adb shell su -c ls -l /data

3) For backup apps, their settings and data, WiFi settings, Calls, SMSes, Wallpapers, use (find on Playstore) root app: Swift Backup

4) Install Androidacy (google for their site) Magisk Modules Manager. Inside find eg Magisk Flash tool (Terminal emulator), and Magisk Bootloop protector modules - screenshots

You can find them also directly on:

Magisk Modules Alternative Repository

An alternative to Magisk-Modules-Repo with fewer restrictions. Now larger than the original! - Magisk Modules Alternative Repository

github.com
[Magisk] zgfg:
If the System is read-only (I wrote you earlier where to check) you can not make hard changes

Systemless rooting - Magisk mounts the changes that modules prepare. You can write your module. If you want to do changes on-the-fly (after the boot) try if Magic OverlayFS module works on your phone. Gave you also where to look for the modules

See also

GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)

Make system partition become read-write (it is also possible without Magisk) - HuskyDG/magic_overlayfs

github.com
[Magisk] zgfg:
When I use custom recoveries (TWRP), I first put TWRP to the ADB Sideload node (go to Advanced, ADB Sideload)

IDK could it work without and generally is sideload supported with your stock recovery

Sideloading is kind of a small protocol, recovery must be in the state to wait for, accept and confirm the sideliaded file

And stock recoveries usually check the signature and only allow installation of the official ROMs
[Magisk] pndwal:
Seems you need to do this:

per section 2 here:

https://droidwin.com/adb-sideload-android-stock-twrp-recovery/

and you should be able to load full OTA stock ROM regardless of whether you enabled ADB debugging in developer options per instructions there...

🤠 PW
[Magisk] pndwal:
This:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88737807

... Also, there are a number of module solutions for font changing (can be fraught however), debloating etc... PW
[Magisk] shoey63:
@Camilo Gil

Forget about old school removal of system apps by making /system rw.

Debloater from F Droid is an excellent systemless debloating tool to use in a Magisk rooted environment.

For all intents and purposes, it works the same as physically debloating.
[Magisk] danweber:
I accidentally hit "deny" in ProxyDroid when it asked for SuperUser rights, managed by Magisk. Now I can't turn it back on.

Google turns up a bunch of hits about clearing the supersu app's memory. I don't have that app, or Magisk has hidden it.

I cleared the program data for Magisk and that didn't change things.

What are my next steps?
[Magisk] BillGoss:
Magisk>Superuser (shield icon)>toggle the switch for ProxyDroid
[Magisk] J.Michael:
No.

"systemless" means when you boot without Magisk active, "system" is back the way it was. You can make it appear as if a file has been changed, or added. Maybe even make it appear as if a file is no longer present. But "/system" is not really being changed, and you will never "recover" space.
[Magisk] zgfg:
Of course not. You cannot delete from READ-ONLY filesystem

Mentioned many times that Magisk mounts over. Hint: mount -o bind

And since SAR is read-only, even if there are few free MB, you cannot write anything there

Again, only by mounting - but the source that is mounted to System is stored to Data (and eats space from Data)

And that saves integrity of your System. It is mounted only when booted to Android, with Magisk and the corresponding module enabled

You boot to Recovery, there is no mount and System is intact

Btw, you see what you did by pushing the use of incompatible custom recovery. How many similar users would want to free few MB from the System, they would irreversibly hard-delete important System apps and would not be able to boot afterwards
[Magisk] J.Michael:
Sure, if you delete something from /data, you are really deleting it, so you are "recovering" the space.

But if you don't do something to "hide" the app, it will probably recreate its data. Some apps flag themselves to be run without you particularly wanting them run.
[Magisk] J.Michael:
I think the bootloop protector detects some number of boots, either within a certain time, or without successfully completing the boot, and then disables modules (probably all modules).

Feel free to go to github and suggest the change to Magisk. Don't take it personally if the suggestion is rejected.
[Magisk] pndwal:
🤔

As I said, RO has nothing to do with SAR (introduced w/ Android 7.1 on Pixel but generally in AOSP from A9)...

www.twitter.com/topjohnwu/status/1174392824625676288

Android 7.1 - 9.0 SAR devices all had RW mountable/system.

2SI (introduced w/ A10) brought RO system on stock devices because it introduced shared blocks/dynamic (super) partitions, ie. modern stock 2SI "ramdisk SAR" devices are consequently locked to RO. 🙃 PW