Hi,
I finally could unlock my Mi 9 this week and flashed TWRP. Everything went fine, I am still fully encrypted and TWRP asks for my PIN and decrypts successful /data
What makes me curious is that the device doesn't ask for my PIN during startup and I can't find any Settings-Option to enable this.
Is my data secure? Does MIUI not mount /data until it is fully booted and asks for my password?
I want to be sure that my data is properly locked if my device gets out of hand.
Related
So if I shut my phone off and turn it back on into fastboot mode and then flash TWRP to boot into TWRP recovery, I can then see all my files and sideload or USB Mass storage status etc.... Doesn't that mean it's not secure?
Secondly I installed TWRP, but now when I reboot it's back in stock recovery. Any idea why that is? Do I have to "install TWRP" Everytime I want to use it?
After some research I discovered that requiring pin at boot fixes this issue. If you don't require pin at boot then your phone really isn't encrypted. Like I read it's like having a bike lock with the password taped to the seat.
Yes, because most Android devices are using FDE encryption. Newer devices running Nougat are using file based encryption, eliminating the need of entering pin at startup while still making your data still pretty secure. For example, iPhone is using both file based encryption and full disk encryption, but I like Android's implementation better, it is more secure imho. In iPhone developer can choose NOT to encrypt app data, idiotic.
My Mi5 was on MoKee rom (mashmallow), with encryption on(it seems to do the encryption the first time I boot MoKee rom, as I input a pin at the time). It seems to work fine: I had a PIN (call it P) set to unlock device. I need to input it every time I reboot device, and TWRP can also use it to decrypt data.
But it turns out I don't like Mokee and would like to use CM 13 instead. So today I booted into TWRP, wiped everything, and flash CM 13 stable build from 12202016. That goes well. First time boot CM 13, it ask me to set a PIN. I just used the same PIN (P). Now CM 13 boots fine. It will ask me PIN once on during boot process, and once more for first time unlock screen (from then on I can use fingerprint to unlock). Not sure why it need PIN twice, but at least I can live with it.
The problem is: now if I boot into TWRP, it will tell me 'PIN incorrect, failed to decrypt data. So I can only go into TWRP without access to data partition, which means it's useless. I have never set a different PIN other than 'P' on this device, so I'm not sure how I could progress with TWRP. I'm using lastest official TWRP for gemini (3.0.2-3). Anyone with more experience, please help. Many thanks.
--EDIT--:
Turns out I need to set "lock screen - input pin when booting" to 'On'. Then I only need to input PIN once during normal boot, and can use that PIN in TWRP to decrypt. It's not intuitive at all, but that solves the problem.
****ing TWRP, i wasted a lot of time on this fking bug
Same issue after new ROM installation
I own a Redmi Note 4 and had a pin (call it Q) that decrypted the data with no issues on startup as well as in TWRP decrypt. Now, recently I installed Resurrection Remix v7.0.0 Android Pie from v6.x.
Now whenever I try to open TWRP and decrypt with the pin Q, it says "decrypt failed" but it works whenever I reboot the device and it asks me to enter pin before startup.
I also could not find "Input PIN while reboot" in the settings, maybe due to new android version policy or because device is already encrypted.
Please help.
TWRP Version: 3.2.1-0
Log:
Updating partition details...
done...
Unable to mount storage
Full SELinux support is present.
Failed to decrypt data.
--EDIT--:
Just downloaded the latest TWRP (3.2.3-1) image from the official site, used "adb push <TWRP image> <location in device>", then "Install" and "Install Image" in recovery and it solved the issue. I used "/sideload" as device location to "adb push" because "/sdcard" wasn't mounted maybe due to encryption.
mrmathematica said:
Turns out I need to set "lock screen - input pin when booting" to 'On'.
Click to expand...
Click to collapse
what are you trying to say on this part? sorry i am lost
Previously I installed omnirom and set a screen pattern now when I rolled back to oxygen OS 5.0.2 I set a different pattern but secure boot pattern is still the old one I've Used in omnirom, I wanted to install new version of that rom now and when i Did reboot TWRP won't decrypt data with my present pattern.
Can someone help me bypass and decrypt the data, I've my important files in it.
With this bug I've to format my data to use my phone but I want my data, help me out.
Have you tried to decrypt data with another TWRP, like BluSpark or acuicultor?
Good evening.
I updated to 19.1 on OnePlus 3t and 5 without any issues, but with my Huawei MediaPad M3 I was faced with problems:
Installation went well, but after reboot Android asks me for a password to encrypt data. Device is in flight mode. ADB not available. Nothing is accessible. Not even a keyboard opens. Just a line and a blinking cursor.
To restore is not neccessary to wipe. Flashing stock boot is enough to boot properly. Read already that many try to wipe data without any success.
Tried manually install. Install from TWRP. Everytime the same result.
Found this posts on GitHub:
https://github.com/topjohnwu/Magisk/issues/1409
Seems that there is an issue with many Huawei devices.
Went back to Magisk 18.0, which still works.
Tried to decrypt data manually. But the Huawei MediaPad M3 has not option in the setting do decrypt data.
It seems that data is encrypted by default, even if no device password is set. Makes for me absolutely no sense to encrypt data without password protection, right?!
Is there any way I can decrypt data via ADB or Magisk without wiping data?
Hi,
I have the same problem. I was able to use a USB keyboard with an OTG cable to type but I never set a password to begin with and of course just pressing enter did nothing. After rebooting into TWRP, installing the 18.1 zip allowed it to work again. I've tried v19.1, v19.2 & v19.3 with the same result. The latest version of Magisk Manager (7.3.2) works just fine.
Hello, I'm trying to remove pattern lock on Redmi Note 10S Mojito without lossing data. I have unlocked bootloader, flashed Nebrassy Unofficial TWRP 3.5.2 (could not find any other "small-sized" recovery), if I use any other recovery I get this error: "FAILED (remote: 'size too large')".
It asks for pattern, when booting to recovery.. I have flashed .zip file for removing pattern. Now when I boot into system, there is no pattern, but can't open any app. Getting "Wait until your device is fully rebooted before opening apps". When I boot into recovery, it still asks for the pattern, which I don't know.
Have also tried to flash around 20 different .zip files for disabling force encrypt. No one worked well. Most of them returned with error while flashing. Others did nothing.
- Developer options: enabled
- USB Debuggin: enabled
- Unofficial TWRP 3.5.2 by Nebrassy: installed
If there is no way, to remove pattern lock, then I would be happy, if is possible to decrypt the data and copy & paste them to the computer.
Please can someone help me with this?
Thank you in advance!