Database Info

[Q] Is ICS / CM9 phone encryption working on HTC ChaCha

Hi,
Does anyone have any insight as to whether CM9 phone encryption is working on the ChaCha rom described on XDA:
http://forum.xda-developers.com/showthread.php?t=1665828
Phone encryption is not listed there as one of the known problems, but CM9 phone encryption problems are mentioned elsewhere on the net.
I installed the CM9 for the HTC chacha without any hiccups. (I installed it after doing a factory reset via CWM from a rooted s-on stock HTC sense rom. I did factory reset, then wipe cache partition, then wipe Dalvik cache, then loaded then CM9 and gapps zip files).
When I tried to do the phone encryption, it seemed to hang or stall on a screen with a green outline of the droid with a sort of lock waistband. The text at the begin encryption screen says the process can take an hour or more, but I left the phone plugged in for about 6 hours. The green outline icon was still there (after entering my PIN at the lockscreen). When I pressed home, it took me to the home screen, but under settings/security the option to encrypt phone was still there so I am assuming encryption did not work.
The other thing to consider was that I was using a 64gb sd card, so perhaps that would make the process take longer (though several hours seems sufficient). I will try again with a 2gb card.
Also, I had not restored any programs or data via Titanium Backup, nor linked to google email/play before starting the phone encryption process.
Thanks!

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

Honestly that's untested at this time. And why didn't you use General section in the ChaCha forums?
I'm curios as to weather it's related strictly to CM9 or not, if it's working on other ports and if it's working on the RC1.
From what I can see the procedure is as following:
Touch Encrypt phone.
Enter your lock screen PIN or password and touch Continue.
Touch Encrypt phone again.
The encryption process starts and displays its progress. Encryption can take an hour or more, during which time your phone may restart several times.
When encryption is complete, you’re prompted to enter your PIN or password.
Subsequently, you must enter your PIN or password each time you power on your phone, to decrypt it.
Click to expand...
Click to collapse
And if CM9 phone encryption problems are mentioned elsewhere then it's mostly a CM bug.

OK, I'm not sure exactly where the problem lies, since there seem to be some reports of it working on some versions of CM9 (perhaps on only some builds and phones).
Also, I tried without the large sd card - same result, it just hangs on the outline screen, rather than continuing and displaying progress.
It would be great to have this, since one of the biggest advantages of the Chacha is its great keyboard, but if the phone isn't encryptable (except with more tedious operations, e.g. tasker) then that sort of defeats the purpose.
Actually, I can't find anything via google about phone encryption working on any CM9 build, though it seems to be working on many ICS phones.
Report of same stall problem with CM9 and Samsung captivate and galaxy, etc:
http://forum.cyanogenmod.com/topic/49617-cm9-and-phone-encryption/
http://forum.cyanogenmod.com/topic/49970-cm9-not-encrypting-phone/
http://forum.xda-developers.com/showthread.php?t=1477920#23742435
Reports of the encryption problem as a CM9-wide issue:
http://code.google.com/p/epictouchcm/issues/detail?id=73
https://plus.google.com/112172895831966524738/posts/YMHhAob6m6W

Type password to decrypt storage?

I've had my Nexus S for a year now and it's been pretty problem free... When it had Gingerbread it had the odd reboot glitch but since ICS it's been solid. I have the bootloader unlocked and had root. I had tried out a couple of custom ROMs and had gone back to stock ICS in anticipation of JB rolling out in July. I got the OTA push of JB in mid July and after a factory refresh have had no problems with the phone until yesterday.
I was typing a text message and my phone rebooted in my hand. It never did complete booting and left me at a prompt that stated "Type password to decrypt storage" and nothing would make this phone boot! Also, since the JB update I no longer had root and Clockwork Recovery no longer worked because I didn't have root... which I wasn't worried about up until now. I had to tether the phone to my laptop reset Recovery using the SDK tools and then wipe everything and reset the phone and reinstall all my apps. Funny thing is I've not been able to find much about this from any of the forums I read frequently... seems there aren't many who have experienced this.
Just wondering if anyone else has run into it...

it's happend for me too. i had to wipe cache and fixed.

Same thing happened to my Nexus S. I have no idea how it came into this "type password to decrypt storage" damned state. I'm trying all passwords and PINs I know but none is working! I'm trying to avoid a factory reset.... Isn't there a way to log in and override this thing, something like forgotten password in emails???

still no solution for this? i've wiped data and cache and still no fix!

I'm facing the same issue: woke up this morning to find my phone asking for a password in order to decrypt storage. Very annoying, since I don't have a very recent backup.
Running CM10.1 nightly 0210 with stock CM kernel. I tried reinstalling CM and wiping cache, but that didn't help. I'll see if I can fix it and and will repost here if/how I fixed it.

gearjunkeez said:
still no solution for this? i've wiped data and cache and still no fix!
Click to expand...
Click to collapse
If you can boot into bootloader (fastboot), try to flash Google factory image.
untar (unrar/7-zip) the tar file and flash the update zip within. This should wipe everything including system.
Code:
fastboot -w update image-soju-jzo54k.zip

kooske said:
I'll see if I can fix it and and will repost here if/how I fixed it.
Click to expand...
Click to collapse
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!

HELP!
I just had the same thing happen to my phone. Can you please dumb down what you just said for me? The only part I care about is how to recover my pictures. I haven't done the factory reset yet as I've been trying every password I can think of and now see that it is a bug and not something I have done. Anyway, I have 3 gigs of pictures of my 18 month old that I will cry if I lose so if you can help me recover them I would really appreciate it. I have tried hooking my phone up to my computer in it's encrypted state and it does not register. Please explain what you did in simplified terms for me as I have no idea what ROM or CWM means. Thanks!
kooske said:
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
Click to expand...
Click to collapse

Wrong pattern after booting TWRP / Can`t decrypt data

Hey guys.
Got a Oneplus 6 running lastest OTA with latest TWRP installed.
Before flash this latest OTA, I was running latest open Beta, flashed by TWRP, with no problems.
Just booted on TWRP today to flash latest Beta again, but when I drawed the patterns, TWRP restarts. Tryed some more times, same thing, put the right patterns, TWRP imagem boots into it again.
Rebooted into system, but the system said wrong pattern now. Can't boot in system anymore too.
Booted in TWRP again, went to File Manager, and deleted these files inside /data/system (Guess I ****ed up even more here)
locksettings.db-wal
locksettings.db-shm
locksettings.db
Now I can boot in system, but it stay stuck on Initializing system on screen, and I can access only configuration using the status bar. Tryed to set the same pattern on security, still don`t work on TWRP decrypting, and system keeps saying Initializing.
Got pretty stuck here, don't know nothing else to try, anyone have any clue on what I can do?

When asked for the pattern in TWRP instead of trying to enter it choose the "do not decrypt /data" option. Then you can format (not wipe) /data. Obviously you'll lose everything, including on internal storage.
And also, it may happen again if you don't flash the no_verity zip. That stops the ROM re-encrypting /data. See this thread for more info.

Looks like some Security Patch downgrade stuff. You flashed an older build, encryption gets messed up because the Security Patch date is older than the one previously installed, you'll have to format your Data partition to decrypt the storage.
As said above, running decrypted will prevent those situtations

Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.

And: instead of a pattern, it's recommended to use a PIN (at least 8 digits) or password (at least 6 letters/digits/specialchars)

remewer said:
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
Click to expand...
Click to collapse
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.

Totone56 said:
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Click to expand...
Click to collapse
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.

remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Agreed, that is what i personally do. I like being able to flash anything and potentially having to format the whole storage without any worry. Using Google Photos, Keep, Doc, ect, using Spotify and syncing every contact really makes life easier.

remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Which is fine if you are only getting this issue directly after ROM flashing or at some other predictable time. But when I was getting it, my lockscreen code/pattern was initially working fine after flashing the ROM, then it would stop working at some seemingly random moment. So the only way I could reliably have any data stored was to run with /data unencrypted. Which I agree is not ideal.

oneplus6 seems damaged following a failed twrp restore

So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.

Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)

I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.

Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.

So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.

I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.

I already stated thats already been done.
I eventually got msm working. and that luckily worked.

@chrcol ..., but you've issues

chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.

Deleted Cache Partition by mistake, HELP!

Hi all,
I recently took the plunge into the Android world of things and loved it. Everything was going according to plan, until I decided to try out the DSU loader and load a GSI package. Based on everything I read it shouldn't had cause any issues, but unfortunately it did. Once I rebooted the phone I received the dreaded "Your Device is Corrupted and Cannot Be Trusted" message. Unfortunately it all went down hill for me from there. A couple of things I know now and shouldn't have done without knowing more information was performing a "Format and Download" option on the phone. Had no idea I was going to loose other partitions that is not created by the flashing of the Rom.
I was able to get the Manufacturer Rom and flash it back to the device. Everything appeared to be working fine until I noticed that I was not getting any data for the battery management option. Another thing I noticed is that now my battery is rapidly loosing it's charge. Could this be related to the Cache Partition not being present? Is there anyway to get the Cache Partition back or recreate it by rooting the device? Any suggestions would be greatly appreciated.
Thanks,
-Glitch