Hi!
My history:
ZTE Nubia Z11 NX531j, Bootloader unlocked, ROOT enabled, TWRP 3.0.2.0 and 3.2.3 (with Mokee9)
Lineage OS 7.1.2 system was installed 2 years ago, the phone was successfully encrypted.
Recently I decided to look at new firmware, installed Mokee 9 with a full wipe, tried to encrypt the phone and get failure, tried without root and magisk on a clean system - the same result.
Turn back the Lineageos 14.1 7.1.2 and got the same problem - phone encryption won't start (tried without root and magisk on a clean system - the same result.)
I tried to figure out the problem on my own, but I couldn't, I lack knowledge.
nx531j:/ # vold cryptfs enablecrypto inplace default_password
vold cryptfs enablecrypto inplace default_password
Aborted
Please help me what you can see to understand the problem.
Related
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
fex42 said:
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
Click to expand...
Click to collapse
Use this recovery:
Pendragon2000 said:
Use this recovery:
Click to expand...
Click to collapse
Thank you, but it seems not to be caused by my TWRP version (3.2.1-0). In the meantime I installed LineageOS 15.1 but did format data again just before rebooting and now data stays unencrypted (does not ask me for unlock pattern in TWRP). Even after installing Magisk v15.0 later, is stays unencrypted . But in MagiskManager there's the checkbox set "keep force encryption" - dont know if that does matter? On my Redmi Note 4 this checkbox is not set.
Same problem here with my Redmi K20 Pro. The problem occurred after I reboot my phone to uninstall FDE.AI magisk module. My phone then encrypts itself. Factory reset, format data, repair partition, re-flashing stock ROM doesn't solve the problem. Have you solved it yet?
Hello everyone,
I did something stoopid: I changed my twrp after wiping system.
Before I removed every protection from my phone (pin, fingerprints, trusted faces)
Now my data are encrypted.
I sent my old rom (crdroid 31-07) via adb push to sidelod-folder and installed it.
Result: TWRP Bootloop
I restored everything as it was before.
Same TWRP, same vbmeta, but my os just won´t start - it keeps crashing and boot into twrp.
Then I flashed latest fastboot rom with "save userdata", flashed my old twrp and vbmeta again, sideload crdroid, installed -> it reboots to twrp.
Is ther any way NOT to format data and get it decrypted?
Thx for helping!
Edit:
Solved it by installing twrp latest by @redispade + his latest rr release (from telegram channel) - It booted up, I can read my data again & now I save EVERYTHING!!!
Today I finally wanted to update a Sony XA2 installation that had been running LineageOS 15.1 for quite a while to 17.1. But of course I wanted to make a backup first. Then I realized that to back up the SMS database I needed root, so I tried to sideload addonsu 15.1. For some reason that failed, and I tried to boot into TWRP to try sideload from there. But now the device only boots TWRP.
Does this mean that the LineageOS installation is gone now? Or is there some way that I can get access to /data/data/com.android.providers.telephony/databases/mmssms.db on the Lineage installation?
0
Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk
Z4_ said:
Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk
Click to expand...
Click to collapse
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.
kurtn said:
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.
Click to expand...
Click to collapse
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.
Z4_ said:
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.
Click to expand...
Click to collapse
There is twrp 3.4 out now. Fixed many android 10 bugs
kurtn said:
There is twrp 3.4 out now. Fixed many android 10 bugs
Click to expand...
Click to collapse
As you might have read in my original post: I was on android 8 and using twrp 3.4. It still did not work.
I have now switched to an unofficial CrDroid ROM with Android 9, as any attempts to restore my backups or install my used ROM lead to errors. This makes the restore of app data difficult, but my smartphone is back to action. I still do not know what caused the errors.
hello,
f*** i ve done an really mistake.
i was on android 12, crdroid 8.1 and use the fingerprint/pin for device locking.
i boot into latest orangefox and install crdroid 8.4 with gapps, after that the device doesnot boot.
i go back into orangefox and read the errror failed to mount 'data'
i cant encrypt the device with orangefox, my pin isnt working either sim pin or android pin.
i flash crdroid 8.1 back with nikgapps, now the device boots but i get the error from android:
encryption unsuccessful, you have to wipe the device.
=> is there any solution to get an working device back, or recover my data, pictures was on the device, not on the sd card
thanks a lot for the answer