[Q]How do I decrypt Z1C with CM11? - Xperia Z1 Compact Q&A, Help & Troubleshooting

I have CM11 nightly installed on my Z1C.
I encrypted the device.
I want to decrytpt it since the GPS is not working when the device is encrypted.
CWM recovery does not have support for encrypted filesystems, so I can't wipe the data partition from there.
I can get root access with ADB on the phone when the phone is turned on, but I can't format the /data partition while it is use.
How do I get rid of the encryption?
I don't care about the data on it.

I simply solved it by installing an original firmware from an FTF via flashtool, that reliably wipes the partitions and thus dm-crypt.

Thank you!
That solved my problem!

Related

[Q] Restart during nandroid backup

Hi to all,
i have a problem.
During the backup from cwm recovery 'recovery-clockwork-touch-5.8.3.1-endeavoru' my phone restart every time. So the process fail and i'm unable to finish the backup.
I'm using a custom rom "Revolution HD 5.0".
Any advice?
Thanks in advance,
Sartan
I have the same issue with revolution 5.1.1
Sent from my HTC One X using xda premium
Hello,
same issue on my phone. Are there any solutions?
Guys, i fixed the problem.
You have to:
- Save all application with astro/titanium
- Save all the datas from sd card into your computer
- Format the 2 giga internal data partition from your phone
- Format the biggest partition (about 24 giga) from your phone.
- Reboot your phone
- install all your app
- restore data
- NANDROID
For me it worked
I had this problem as well.
The problem is (best guess) kernel oops when accessing certain files on the partition.
In my case, it was one of the files in /data/lost+found/... - whenever it was stat()ed or read the phone would reboot.
Let's hope we're not having a defective flash blocks but just a b0rked filesystem.
The worst part is, that without USB debug in recovery, it can't be repaired, because it can't be unmounted once booted. So there's no hope of ever recovering it without full wipe :/
And in this case, it can't be backed up because recovery doesn't allow selective backup of folders on a partition, and it doesn't just dump the partition image for some reason but tried to reas the files - which reboots the phone.
It probably could be solved by chefs in ROMs or by recovery developers by providing an option to run fsck on the filesystem before it is mounted.
zvieratko said:
I had this problem as well.
The problem is (best guess) kernel oops when accessing certain files on the partition.
In my case, it was one of the files in /data/lost+found/... - whenever it was stat()ed or read the phone would reboot.
Let's hope we're not having a defective flash blocks but just a b0rked filesystem.
The worst part is, that without USB debug in recovery, it can't be repaired, because it can't be unmounted once booted. So there's no hope of ever recovering it without full wipe :/
And in this case, it can't be backed up because recovery doesn't allow selective backup of folders on a partition, and it doesn't just dump the partition image for some reason but tried to reas the files - which reboots the phone.
It probably could be solved by chefs in ROMs or by recovery developers by providing an option to run fsck on the filesystem before it is mounted.
Click to expand...
Click to collapse
So the problem can be solved only by wiping right?
For me it wasn't a problem, i wiped and then i backup the rom.

[FIX] [TWRP] [RECOVERY] /system partition not mounting in recovery

I had come across this bug in TWRP recovery where the /system partition was unable to mount.
And i wasn't able to flash any new ROM or even backup current ROM.
Hopefully I had another ROM backed up before and I simply formatted the system and VIOLA! the problem was gone.
I posted this for anyone who might get such a problem in the future and doesn't end up cursing themselves.
Its a common bug and very easy to fix. So, Happy Flashing!
This basically work for any partition not mounting error.
Hit thanks if it helped
Help me fix my twrp
Pls, I have been on this platform for some time now. I have a challenge presently with my phone Tecno LB8A. I have been trying to upgrade it to version 10. I have unlocked the bootloader, rooted it and also flash twrp into it. I downloaded Lineage 17 and havoc but I bricked my phone severally. In twrp, I discovered there is no system partition there. Pls I need your guide on how to make the system appear. What I have on the partitions there are: dalvic cache, cache, data,sdcard, otp and internal storage. The second question bis how do I flash Lineage into it without bricking the phone

TWRP can't mount sdcard or /data

So I flahed the new MDB08M image and since it uses the "I" boot image I went ahead and flashed the modified boot.img and flashed TWRP and used it to root as I didn't have SuperSU zip on the device yet. After flashing the new system I didn't do any factory reset.
Now TWRP says that internal storage is 0mb and it can't mount /data. Every time I boot into it, it comes up with the screen asking me if I want to modify /system or leave it read only. I check the box to not show it again and swipe to modify.
I've tried using adb again to flash recovery but it didn't help. Any suggestions?
Edit: bootloader also sais I'm secure, and in security it sais I'm encrypted..
TWRP can't decrypt /data on the N5X yet. You can format from TWRP, but you'll lose the contents, of course.
PhoenixTank said:
TWRP can't decrypt /data on the N5X yet. You can format from TWRP, but you'll lose the contents, of course.
Click to expand...
Click to collapse
I thought by flashing the modified boot image that would decrypt? It did on MDB08I..
The modified boot just changes flag to encrytable instead of force encryption. It doesn't actually decrypt the drive contents. Once you wipe it then you can mount data in TWRP.
eqjunkie829 said:
The modified boot just changes flag to encrytable instead of force encryption. It doesn't actually decrypt the drive contents. Once you wipe it then you can mount data in TWRP.
Click to expand...
Click to collapse
so just factory reset in TWRP?
Edit: reflashed firmware, flashed modified boot and did a factory reset in stock recovery. reflashed TWRP and all is good. thank you

[SOLVED] Help! "encryption unsuccessful" message!

I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!

how to decrypt after installing twrp

i have twrp installed using the bootloader unlock bypass.
how do i go about decrpyting the phone so i can install stuff from twrp in the future?
cheers
This question was lost with time.
If i seen it before i would have answered it before.
Wgen you first install vbmeta skip partition it wipes your security options. Messing with the encryption of your data partition.
The only way to gain access to the data partition again is to format the data partition and start the phone fresh.
I assume since this post is 2 months old you made the choice already to format data to gain access to you drive once more.
As long as you keep your new vbmeta through all your new zip installs you should be able to access your data on each update.

Categories

Resources