i am using note 9 with twrp and magisk installed i want to use google wallet but its asking me to encrypt device.. i tried to encrypt it but its keeps saying encryption failed and reset device even i tried to reset but its still showing same.. so i want to know is it possible with magisk to simply bypass encryption on apps which required it? i mean how can i run apps which require encryption with enabling encryption?
junaidali15 said:
i am using note 9 with twrp and magisk installed i want to use google wallet but its asking me to encrypt device.. i tried to encrypt it but its keeps saying encryption failed and reset device even i tried to reset but its still showing same.. so i want to know is it possible with magisk to simply bypass encryption on apps which required it? i mean how can i run apps which require encryption with enabling encryption?
Click to expand...
Click to collapse
Yes, posible, try this module -
Fake encryption
Is there any way to fake that system has encryption turned on? I do not want to encrypt my phone but my local bank app need encryption in order to use finger print login. Is there way to fake encryption to that app?
forum.xda-developers.com
Related
Maybe I'm doing something wrong, but after trying absolutely everything, flashing Supersu v2.68 prevents the ability for my Nexus 6P on MHC19I to encrypt. This applies to encryption on first boot or through security settings. I'm also using the latest modified TWRP for MHC19I.
Is that an expected behavior?
mylios101 said:
Maybe I'm doing something wrong, but after trying absolutely everything, flashing Supersu v2.68 prevents the ability for my Nexus 6P on MHC19I to encrypt. This applies to encryption on first boot or through security settings. I'm also using the latest modified TWRP for MHC19I.
Is that an expected behavior?
Click to expand...
Click to collapse
It's a known issue. You need to be unrooted for the encryption procedure to work. You can root again after encrypting.
Chainfire said:
It's a known issue. You need to be unrooted for the encryption procedure to work. You can root again after encrypting.
Click to expand...
Click to collapse
If SuperSU doesn't delete the verity key from the ramdisk when it patches the boot.img, wouldn't encryption still be possible? Or are those two things unrelated?
The systemless root files live on an image on /data, as such /data is always in use and cannot be unmounted. It needs to be unmounted to change the encryption.
Hey,
So I tried to encrypt the phone without any warning that it is not compatible with cm12.... thus found myself fixing a bootloop. So how can I encrypt the ****, what encryption alternatives are safe to use with cm12? Thanks.
Nevermind. Solved it
I have a Nexus 6 stock and would like to share my recent experience with the community about what happened to me yesterday.
I installed Magisk 16.7 at the beginning of August and finally I was able to hide all apps from root, including Android Pay which said I was allowed to pay contactless. Hooray!!!
Yesterday something odd happened. I had troubles with my battery stats so -long story short- I chose to wipe the cache from stock recovery.
Upon reboot, Magisk lost root. I had a copy of the Magisk zip file handy so I booted TWRP and flashed the zip. Did not work.
So I spent my entire evening applying OTA N8I11F then flashing either Magisk zip or the patched boot image, but without success. Magisk was never enabled.
Only after wiping cache, reflashing OTA, deleting /data/su.img via TWRP, deleting the entire Magisk app with its settings and reflashing the patched boot image I was able to get Magisk to work again.
I am sure I didn't "dirt" the OS by running the steps above in their order in Flight Safe mode.
But now it looks like my phone is like doomed forever. Despite I applied MagiskHide to all apps except the ones I want to be root-enabled, Play Store reports my device as "not certified".
Android Pay does not start, demanding an update to Google Pay. But Pay is now incompatible with my device and won't download. (I think Google Pay is an upgrade to the Android Pay app)
At the moment I can still find Netflix, since Netflix won't appear on rooted devices for listing.
Today I was looking into SafetyNet and my attention was caught by:
Device Status Value of "ctsProfileMatch" Value of "basicIntegrity" Certified, genuine device that passes CTS true true Certified device with unlocked bootloader false true Genuine but uncertified device, such as when the manufacturer doesn't apply for certification false true Device with custom ROM (not rooted) false true Emulator false false No device (protocol emulator script) false false Signs of system integrity compromise, such as rooting false false Signs of other active attacks, such as API hooking false false
Click to expand...
Click to collapse
I don't know if this existed before and if Magisk Hide can hide the bootloader status to Play apps.
I am confused. Has something changed very recently? SafetyNet test reports failure despite it reported success in the past.
Anyone found this happening too? Any ideas on how to restore Pay?
Have you tried wiping data of pay, play store and play services?
Also, I think there's a magisk module for editing build props so eventually that could be used or modified for unlock status - yet that's just a speculation by me...
Gesendet von meinem Moto G (5) Plus mit Tapatalk
For Certifying The Device & Pass The SafetyNet, Check This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
gothicVI said:
Have you tried wiping data of pay, play store and play services?
Click to expand...
Click to collapse
Luck that worked. I didn't delete play services' data as I was afraid it would have deleted my accounts and SMSes.
Device is now certified. Android Pay does not demand me any update, asks me for adding cards.
Google Pay still unsupported. Not a problem.
Okay, problem solved.
Fiuuuuuuuuuuuuuuuuu
I have a similar problem too when I root from magisk The phone said me "Data partition corrupted" and I choose reset button but I was aiming root without data loss but my root hadn't gone to anywhere but my phone was unable to pass safetynet after a long time I tried to delete cache to accelerate my phone but when I opened my phone I got error messages from my root apps and when I tried to open magisk it stucks in magisk logo.I still can't pass safetynet too :crying:
igalhan said:
I have a similar problem too when I root from magisk The phone said me "Data partition corrupted" and I choose reset button
Click to expand...
Click to collapse
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
djechelon said:
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
Click to expand...
Click to collapse
Ok but I reseted my phone and it fixed could it be about forced encryption
---------- Post added at 05:16 PM ---------- Previous post was at 05:15 PM ----------
djechelon said:
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
Click to expand...
Click to collapse
I didn't installed twrp it's from odin
Hi. I'm running Nitrogen OS (latest Oreo version) and i noticed something really funny and weird. I somehow encrypted phone on this rom via Magisk (asking for pin on boot,in twrp as well). But recently i unchecked that "Preserve force encryption" and after some time i rebooted phone. I noticed that android not asking for pin on boot (and twrp the same). So i somehow can control/remote encryption. Really weird.
PS:Can someone explain how tf is this possible?
Pheggas said:
Hi. I'm running Nitrogen OS (latest Oreo version) and i noticed something really funny and weird. I somehow encrypted phone on this rom via Magisk (asking for pin on boot,in twrp as well). But recently i unchecked that "Preserve force encryption" and after some time i rebooted phone. I noticed that android not asking for pin on boot (and twrp the same). So i somehow can control/remote encryption. Really weird.
PS:Can someone explain how tf is this possible?
Click to expand...
Click to collapse
I've had something similar happen a couple of times with Magisk. It seems to remove the on-boot password which allows TWRP to also access the data.
It doesn't actually remove the encryption - you have to reformat the data partition to do that.
You can set a new on-boot password by setting a new password (it can be the same as the current one) and require it to be used to boot the phone.
Sent from my OnePlus3T using XDA Labs
After unlocking bootloader and flashing Magisk-patched boot.img, says "device is not certified". Would this cause any trouble in the future or even now? I can download apps so seems like it's nothing to worry about, just wanna make sure.
That's a standard message that comes up on any Android phone starting since Marshmellow I think? But no that screen is nothing to be concerned about, just showing that your bootloader has been unlocked.
ColdFyre33 said:
After unlocking bootloader and flashing Magisk-patched boot.img, says "device is not certified". Would this cause any trouble in the future or even now? I can download apps so seems like it's nothing to worry about, just wanna make sure.
Click to expand...
Click to collapse
Not much to worry about but if you wipe data and cache on pstore then reboot, it will usually certify
As previously already stated, just force close and delete app data + cache from the play store app, reboot, and it should show as certified (only if safetyNet previously already passes of course!). Keep in mind that after rooting, you need to enable the HideProps module in Magisk to force basic attestation by emulating an older device (e. g. a Pixel 3a). Otherwise safetyNet will fail and your device won't certify.