Lollipop Leak Available for the Sprint Galaxy S5

Since the Android 5.0Lollipop’s official release not too long ago, we’ve seen … more

CPU Spy Gets an Android Lollipop Makeover

At some point in the distant past, you probably heard of CPU Spy for Android by XDARetired … more

Amazon Fire TV Stick vs Chromecast – XDA TV

There is no doubt that Amazon is a huge player in many markets, and they want to be a huge … more

Fight the Heat and Conserve Battery with EaseUS Coolphone

Memory hungry Android applications are often responsible for making our device … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Problem with encryption on CM11

OP Zero-V

6th May 2014, 11:15 AM   |  #1  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Hi, installed FXP318 on Xperia M and cannot encrypt phone, logcat says:
"Orig filesystem overlaps crypto footer region. Cannot encrypt in place."

Found this topic while googling
forum.cyanogenmod.com/topic/82292-cm102-encryption-does-not-start-stuck-at-splash-screen/

Formatting /data from recovery doesn`t fix issue so far.

I assume it is a bug, how can I address it to developers?
Last edited by Zero-V; 6th May 2014 at 03:10 PM.
The Following User Says Thank You to Zero-V For This Useful Post: [ View ]
6th May 2014, 02:36 PM   |  #2  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Something is terribly wrong with encryption on FXP318 imho. So, according to link above and other sources, "It needs to make sure the filesystem doesn't extend into the last 16 Kbytes of the partition where the crypto footer is kept." I boot to recovery and formatted /data:
Code:
# mke2fs -T ext4 -L userdata /dev/block/mmcblk0p27 2133871
I made 512kb, 32kb give the exact error.

Next, encryption didn`t start either and phone just rebooted, logcat showed "unmounting /data failed" before reboot. Google lead here
code.google.com/p/android/issues/detail?id=58073

Script
Code:
# while true; do lsof | grep /data; sleep 0.2; done
showed that sensord is not allowing unmounting. So I did
Code:
# killall sensord
before final click to "Encrypt storage".
Finally, encrypting began and completed successfully (I thought so).

After reboot, phone is asking for passphrase and when I type it, green "decrypting" robot appears for a second and then black screen and phone is totally hanged and unresponsive, only removing battery helps.

#$ck!
I`m out of ideas
7th May 2014, 11:47 AM   |  #3  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Anyone? There is no user with encryption enabled??

Could please someone point this thread to PecanCM or in dev thread, as I cannot write there
forum.xda-developers.com/showthread.php?t=2584956
Last edited by Zero-V; 7th May 2014 at 02:42 PM.
8th May 2014, 10:27 AM   |  #4  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Ok, I continue my monologue FWIW

Encryption in stock firmware works as it should, w/o problem. Updating to CM11 lead to "Unsuccessful encryption" and phone resetting. I could encrypt with killing sensord though, but decrypting is still lead to unresponsive phone.
8th May 2014, 09:10 PM   |  #5  
paper13579's Avatar
Senior Member
Flag dublin
Thanks Meter: 255
 
687 posts
Join Date:Joined: Oct 2013
More
Quote:
Originally Posted by Zero-V

Ok, I continue my monologue FWIW

Encryption in stock firmware works as it should, w/o problem. Updating to CM11 lead to "Unsuccessful encryption" and phone resetting. I could encrypt with killing sensord though, but decrypting is still lead to unresponsive phone.

Why would you want to encrypt your phone?

Sent from my C2004 using XDA Free mobile app
8th May 2014, 11:35 PM   |  #6  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Quote:
Originally Posted by paper13579

Why would you want to encrypt your phone?

Why would anyone don`t? In the world of security concerns and privacy invasions...
13th May 2014, 11:19 AM   |  #7  
OP Junior Member
Thanks Meter: 3
 
18 posts
Join Date:Joined: Apr 2014
Ok, FXP319 doesn`t fix issue. Also I checked FXP316 and FXP309 - the first with Xperia M support.

The Following User Says Thank You to Zero-V For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes