Question Bypass pattern lock without lossing data? - Redmi Note 10S

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!

Related

TWRP can't decrypt /data on CM12.1

I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.

twrp failed to decrypt data

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

Data decryption error - secure boot pattern

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?

Issue: Huawei device asks for password to decrypt data after update to 19.1

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.

password on startup while encrypted / secure startup option

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.

Categories

Resources