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
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.
So I have seen a few threads depicting this bug/error/whatever it is, that when starting Android it asks for a PIN, no keyboard shows up at all.
I recently changed my password, and I guess absentmindedly checked yes to asking for a password on boot. However, after the device's first reboot with the new password, I can't enter anything when it asks me to. On the bottom of the screen, there is an 'Emergency Dialer' button, but I cant even press that. Is there any way to fix this? I can decrypt the system through TWRP with the password just fine, so I know it's the right password, I just cant enter anything on the Android side of things. I saw some suggestions being flashing a keyboard (no idea how to do that), reflashing the ROM, even using an OTG cable (which I have, no keyboard though) but I don't want to mess up the device any more by doing any of these if it was somehow to mess with the password or encryption. Any suggestions, or idea as to why this happens? Any help is much appreciated.
Update: I tried to flash a Nandroid backup from before I started having this issue, and its still asking for a PIN.
Update 2: Wiped /system/, flashed ROM and STILL have the pin screen. TWRP still decrypts with the current password, not the one from the Nandroid backup.
I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.
Anova's Origin said:
I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.
Click to expand...
Click to collapse
Gave that a shot, reflashed my ROM both dirty and clean, restore from a very old nandroid backup, nothing has worked..
Did a system wipe and I'm still having the issue.
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.
Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Click to expand...
Click to collapse
If a physical keyboard is the last option, I'll have to wait until tomorrow to get one I guess (I only have a laptop).
I know there's a way to use adb to input keyboard commands, but although I know I had debugging on it doesnt work on whatever this screen is called.
Thanks for the help though!
Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.
Click to expand...
Click to collapse
Would deleting the Swiftkey folder from /system/app or /data/app mess up anything? I'm pretty sure that Swiftkey is the culprit here.
No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.
Anova's Origin said:
No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.
Click to expand...
Click to collapse
Uninstalled it through file manager, and still no keyboard came up.
This is the most stubborn issue I have ever encountered, quite literally done everything.. except using a physical keyboard but even then, this issue shouldn't have persisted if I've wiped this many times..
You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.
Anova's Origin said:
You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.
Click to expand...
Click to collapse
Flashed a brand new rom instead, got keyboard up but it's telling me that my pin is incorrect. Still stuck
Wrong password at boot is a far more common problem. Fix
For me, turning off display and turning it back on popped up a keyboard, when it was an issue. Somehow fixed at one point.
Luckily i recently acquired the oneplus 3t and in one of my actions in preparing the device for daily use i had the same issue after I install a [MOD] zip, the only quick fix that work 4 me was boot in twrp recovery and wipe factory reset system dalvik / art cache, install oneplus 3t firmware
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/
just keep good 1 or 2 backups b4 u go crazy (or look for revert file) :fingers-crossed:
did you guys figure this out
I used the fingerprint sensor with no problem after rooting with magisk 17.6 (i think). But all of a sudden it wasn't working in any apps, including magisk manager but still works on my phone's lock screen. When i go to turn on fingerprint authentication for say lastpass or magisk manager it just says fingerprint failed without the opportunity to check my fingerprint like it usually does. Updated to magisk 18, same issue. Also tried a complete unroot and re-root and still not working. Even when i was no longer rooted the issue still occurred. Using a huawei p10(vtr-l29) on android 8.0.0.376(C432).
TIA
EDIT: heres the logcat of what happens when i try enable fingerprint authentication in magisk manager https://1drv.ms/t/s!Aqd1jJ_Y63Gpg7d9GM2_6ZRtB3ZXiA
Hi, I lost the finger print just now after updating to Magisk 18...
Ok, it is OK now, just after a reboot..
Zzrman said:
Hi, I lost the finger print just now after updating to Magisk 18...
Ok, it is OK now, just after a reboot..
Click to expand...
Click to collapse
I've got it fixed now, had to do a factory reset and update to 8.0.0.382. After that I had a safety net CTS mismatch so I had to change the device fingerprint to pixel 3 with the props module via shell
I have the same issue, but to be honest i am kind of lost with your explanation- Can you be more specific, please?
aalmeida1972 said:
I have the same issue, but to be honest i am kind of lost with your explanation- Can you be more specific, please?
Click to expand...
Click to collapse
It was a while ago so I can't remember what I did. Just backup your phone, restore stock recovery and factory reset device. Then start over.
Have a new phone now so can't be of much help sorry
I rooted with magisk 20, solid explorer had a root popup and was granted but xposed never got the popup so was auto refused, is it normal for some apps to just not get root?
I updated to magisk canary and xposed then got the popup and root was granted BUT I'd rather not use a canary/beta build of anything so ideally would like to use magisk 20 stable.
Xposed modules are working APART from exi for swiftkey, has anyone got this working or does it just not work on miui 11?
Xposed mods that work on miui? I've used gravitybox since the day it was released but I have a feeling it breaks miui?
I'm quite happy to use miui 11 stable (android 9) so is there really a need to flash miui 11 beta (android 10)? What are the benefits, if any as like I say, I'd rather not use betas.
I only got to unlock yesterday so flashed a stable miui 11 build because it has options to turn individual sims off, this is basically my 'must have' feature in a rom. I know lineage has it but lineage is a bit plain and boring to be honest, is there a good custom rom (android 9 or 10, not bothered) that has the separate sim option?
I ran an ADB script I have to 'delete' a load of stock apps and rubbish I dont need or want, I know they arent really deleted but now I'm rooted I can completely delete them with SDmaid or similar, phone runs fine as it is with them deleted as it is, but would ACTUALLY removing them from the phone be any different? Could things suddenly go wrong because they arent there? Even though they are frozen now or whatever they are.
Boot animation? Is it just a delete and replace /system/media/bootanimation.zip?
Mii cloud and associated stuff? I dont use need or want any of it, all miui apps are gone except this which I only kept on until I unlocked the bootloader which I now have. Can I delete/remove it all? I dont want themes or cloud or security or any of their stuff on there at all but am fine keeping it on if the phone will go wrong without it.
Thanks for any/all/some help
EDIT> got exi working, needed edexposed sandhook and I was using the other one.
Magisk v20.1 not worked for me too, had to revert to v19.3. I have Mi 8, MIUI 11 Android 9, xiaomi.eu. With MIUI 10 Magisk v20.1 worked just fine. Some security changes... Notice that to lock the screen (user app) now we have permission, no root needed as before.
mymihov said:
Magisk v20.1 not worked for me too, had to revert to v19.3. I have Mi 8, MIUI 11 Android 9, xiaomi.eu. With MIUI 10 Magisk v20.1 worked just fine. Some security changes... Notice that to lock the screen (user app) now we have permission, no root needed as before.
Click to expand...
Click to collapse
I tried miui 11 (android 10) and although I can't remember all the issues I had, there were on screen alerts for things that android 9 didn't have, so I went back to miui 11 (android 9).
I remember the lack of location options, just ON or OFF was annoying, the playstore took ages for an app to even start downloading, the video lockscreen was hit and miss even if it worked at all... And more little things that collectively annoyed me enough to drop back to 9.
I'm currently on lineage but even now I've a problem, I can't turn encryption off (I never turned it on) so everytime I boot to twrp it's asking me for a decryption password that I've never set up, so God knows what that is. I have to press cancel and then I can't use the storage, flash anything OR NAND back up
Never touched the encryption so can't help you, sorry.
mymihov said:
Never touched the encryption so can't help you, sorry.
Click to expand...
Click to collapse
Neither have I!!
robneymcplum said:
I tried miui 11 (android 10) and although I can't remember all the issues I had, there were on screen alerts for things that android 9 didn't have, so I went back to miui 11 (android 9).
I remember the lack of location options, just ON or OFF was annoying, the playstore took ages for an app to even start downloading, the video lockscreen was hit and miss even if it worked at all... And more little things that collectively annoyed me enough to drop back to 9.
I'm currently on lineage but even now I've a problem, I can't turn encryption off (I never turned it on) so everytime I boot to twrp it's asking me for a decryption password that I've never set up, so God knows what that is. I have to press cancel and then I can't use the storage, flash anything OR NAND back up
Click to expand...
Click to collapse
Had this issue back when I had a Motorola X4 and Lineage OS 16. What you need to do is remove the password/pattern/pin from the OS (fingerprint, face unlock also ... what you have) than it will work.
MirceaViP said:
Had this issue back when I had a Motorola X4 and Lineage OS 16. What you need to do is remove the password/pattern/pin from the OS (fingerprint, face unlock also ... what you have) than it will work.
Click to expand...
Click to collapse
Cheers.
I only had the bloody lock because I couldnt get past set-up without it
robneymcplum said:
Cheers.
I only had the bloody lock because I couldnt get past set-up without it
Click to expand...
Click to collapse
BTW you can't Backup (to Google) unless the lock is removed again. You can re-add it once you are done.
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