hi,
I just rooted my phone XT1072 and install lineage OS 14.1
As the phone was empty, i wanted to test encryption. So i launch encrypt function with success because the status is now "crypted" in "Parameters / Security / Encrypt the phone".
however, during encryption, the phone restart several times, and i received few messages as "google service stop working"
So i tried to unencrypt the phone to revert as beginning after the install of lineage os.
So i reinstalled lineageos 14.1, open gapps, wipe data/cache/system partitions but the status stays "encrypted" in "Parameters / Security / Encrypt the phone".
did i make a mistake ? how can i get back to status unencrypted
thks
Wipe data, cache, internal storage and dalvik.
Related
I am in trouble of loosing all my userdata after following the below process:
1. I was on stable 4.5.1 and not encrypted.
2. flashed blue_spark 8.52 recovery.
3. Reboot to recovery and full wiped (except user data).
4. Flashed OOS beta 18 and Magisk 14.3.
5. Rebooted and waited for 20 min but was still on rebooting process.
6. Force rebooted to recovery and alas!, twrp asking for decrypt password!!!
7. Reboot to system and message appears as 'Encryption Unseccessful'
I am not been able to access any partition including userdata from TWRP (as it's asking password), OOS also not booted as well.
Now I will be grateful if someone have any knowledge to skip TWRP password and provide access to userdata to recovery/copy data (photos/files etc) from the device before format userdata and start over again.
If your data was previously decrypted then disable encryption, format data, install a ROM that does not enforce encryption, then try looking on the Play Store for photo recovery apps.
Note that it will not be possible to recover data from the encrypted part of the device. If you left it running for 20 minutes, the chances are your data is almost entirely gone at this point.
Like stated above, your data is probably destroyed since you interrupted the encryption process.
Have you tried "default_password" as the password in TWRP?
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?
So, quick explanation. Pie update showed up on my OP3T and I have an unlocked bootloader, TWRP 3.3.0-1 and Magisk 18.1 on OOS 5.0.8 (Oreo). Additionally I had a second user account and a Work Profile on my main account.
After reading on the decryption issues (and against my better judgement), I decided that maybe it could work through System Updates since it detected root and was going to install the full package. Big mistake. Got a "Decryption unsuccessful" and sadness.
I had of course taken a full TWRP backup to be safe.
I'm going to put the detailed explanation below (hidden) because it's quite long.
Now in more details. Along with the TWRP back up, I had an oandbackup -backup- of all apps (main and secondary account, but not work) and manually copied all internal storage files on my PC. After the "Decryption unsuccessful" message, I pressed the "Reset Phone" button (probably a stupid decision) thinking I'm good since I have a backup. Phone rebooted, with TWRP replaced (as expected), and I'm in the new OS. Played around a bit in Pie [added my account, registered a fingerprint and PIN, connected to WiFi and checked a few apps] and then I thought, "ok, time to go back", and then it happened.
I rebooted the device and it asked for password to boot (which was the PIN I added in the OS), and then rebooted again in Fastboot to flash TWRP again in order to restore the backup.
TWRP flashed successfully and I copied over my backup. Restored System, Data and Boot, wiped Dalvik & Cache, rebooted, shows the Oneplus logo, gets stuck for a bit and then goes to Fastboot. Ok...probably messed up somewhere, let's try again. Same thing.
I guess the notion that I had the TWRP backup made me feel safe, because I continued to experiment.
After a full 24hours awake trying to restore my phone to its previous state, I have the following:
Restoring System, Data and Boot results in the device booting and showing the Oneplus logo and then after a few seconds, going to Fastboot.
Restoring EFS, Recovery and/or Cache makes no apparent difference.
Restoring Data and Boot, but System Image instead of System makes the device boot and start a lengthy process (possibly of encrypting the entire Data partition) lasting about 2hours, during which the device becomes hot enough (~45C / ~113F) that holding it for more than a couple of seconds is very uncomfortable. After it finishes the lockscreen has my wallpaper, app notifications (like VPN) show up and the second account is there, however my old PINs for either accounts don't work and the Data partition can no longer be accessed in TWRP
Code:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
[COLOR="red"]Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (No such file or directory)[/COLOR]
Full SELinux support is present.
[COLOR="Red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
When Data is inaccessible in TWRP, only formatting it can bring it back (empty, of course). And then it needs to be formated to F2FS again as well (Oneplus uses F2FS for the Data partition).
Flashing the Oxygen OS 5.0.8 zip file after restoring System works the same as restoring with System Image.
The closest I've come to restoring my device to how it was before is either:
Restoring System, Data and Boot , in which case booting ends up in Fastboot.
OR
Restoring Data and Boot, and System Image, and then not being able to login (plus, no access to Data from TWRP).
I have literally no idea what else to do. If anyone has any idea or suggestion, it would be greatly appreciated.
I'd rather wait for some suggestions before trying to flash other zip files that deal with encryption, since I never had to do that when I first rooted with Magisk.
------------------------------------------------------------------------------
How the device is supposed to be:
Bootloader unlocked
TWRP Recovery 3.3.0-1
OxygenOS 5.0.8 (Oreo)
Magisk 18.1
Main user account
Secondary user account
Work Profile (with Shelter) on Main user account
What I have available:
Full TWRP backup of all partitions [Data, System, Cache. System Image, EFS, Recovery, Boot]
oandbackup backups of Main & Secondary user accounts (apps and APKs)
Manual file backup of Main user account's Internal Storage
All OxygenOS Oreo zip files that Oneplus was releasing over time
TWRP images (3.2.1-0 and up)
Stock OxygenOS recovery (they used to have it available)
Magisk Installer/Uninstaller/Manager APK
Time on my hands
Sleep deprivation points
Enough will to live
So ...today i decide update my mi8 from lineage os 16 to 17.1 .
before jump to 17.1 i go to setting and download one update of lineage os 16 that i have there and go to twrp to install , when i slide i got an error saying that i need mi firmware superior to 9.6.20 (something like that) , so i look and download the firmware V10.3.5.0 because was the most recent for android 9.
go twrp and install the firmware and after reboot the problems start. mobile restart , mi logo , LOS animation and after a minute reboot and go twrp and stay like that .
so i decide download de 17.1 and install it.
i got stuck on LOS animations for while and after a factory reset on twrp the phone finally boot.
When i start using the phone i start getting some weird stuff.
- if i go gallery its say " no storage. no external storage available"
- if i go camera say " insert an sd card before start using the camera"
- all folder are encrypted
i try different twrp to resolve the encrypted folder and nothing, plus i lost all my data and at any point i chose wipe all data.
anyone can help me ? im googling for 4h and nothing
Did you format data ?
Not wipe, I mean format.
Otherwise backup your data and format.
Clean install
Installation:
Reboot to recovery (TWRP recovery for Mi 8)
Format /system, /data and /cache
Install MIUI Q based firmware
Install LineageOS zip package
Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
hello can anybody help me please
i have forgotten my pin so i used this way to bypass it
rebooted to recovery and selected cancel in decrypt data
Because i don't remember what it was
and deleted what i have found form those files
--------------------------
recoverablekystore.db
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
--------------------------
now my phone opens up but stuck after lock screen at phone is starting
Note: i can enter notification bar and phone settings
could you please guide me how to fix it without wiping the data
ROM: CRDroid 6.13
TWRP: 3.4.0-10 by mauronofrio
@M.WeWe
This sounds like the issue with early Pixel Launcher Mods.
When disabling / removing the module, it caused exactly your problem.
Is your device rooted, did you use such a model and removed it recently?
With a root explorer (or within TWRP File Manager), navigate to:
data/system and delete the "package_cache" folder, then reboot.
This fixed the described issue in the past.
I've been looking for a solution to the same problem for a month.
After installing recovery the memory was encrypted and No os warning came.
It's been in my phone for the last 3 years.
goddamn google
I don't know if I can find a solution without losing the memory.
My nerves are gone now.
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
selaam34 said:
When I install Aosp or stock rom, it restarts at startup.
I installed a middleware but could not access the memory.
Click to expand...
Click to collapse
Whenever you switch the ROM you have to (!) Format Data - it's described in any good guide for how to install a custom ROM to Xiaomi
Formatting Data (that includes also Internal memory) establishes the new filesystem for the new ROM, ie for its encryption - that's why Formatting (not Wiping - wiping wipes the files but keeps the old filesystem) is required