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
Related
NOTE: This is for the Verizon Wireless Samsung Galaxy S3 SCH-I535
Since I'm a new member I wasn't allowed to post this into the developers forum and before I continue: YES, I have searched valiantly for a fix to my particular problem and I spent the entire day new years and most of the day today trying to get CM10.1 to run on my SCH-I535 but ran into problem after problem. Every time I installed any version of CM10 or higher I ran into multiple problems: mainly being that I wasn't able to attain signal, the keyboard wouldn't load or there would be multiple problems with initial setup including having to restart during install so many times I gave up. In the past two days I have Odined back to stock at least 15+ times trying to get CM to run and now that it finally is I believe this is worth sharing.
Before I continue I should mention that your phone should be properly working so if you're in stock and you can't make phone calls or your IMEI is messed up then none of what I'm about to mention is going to work. After you Odin to stock using Root66.tar (http://www.megashare.com/4384479) then type *2767*3855# to reset to factory defaults everything should be running correctly. If not you may have bricked your phone or you have bigger problems for which I cannot help you and I apologize. There's also a torrent file available of the above stock tar file that downloads much faster here: http://forum.xda-developers.com/showthread.php?t=1840030.
So I assume, before I start this, that if you're on these boards you know how to properly root, unlock and flash then recover your phone through CWM 6+. If you do not know how to do this, then you will need to before continuing on.
Use this link: http://forum.xda-developers.com/showthread.php?t=1762709
Now follow Section 1 and pay attention to detail because if you don't you can mess something up and end up having to backtrack which can take valuable time and be amazingly frustrating.
Once these things are done you will need to reboot your phone back out of Recovery mode so you can properly move the necessary zip files onto your internal SD card.
Download CM10 Stable, you can find this here: http://get.cm/?device=d2vzw&type=stable
And download Gapps 4.2.1 here: http://www.teamandroid.com/gapps/ (I used version gapps-jb-20121212-signed.zip)
Put these files on your internal SD card and use EZ Recovery to Flash and then Reboot Recovery, I need to mention as well that when I dragged both of these zip files onto my internal SD I had EZ Recovery open while doing so. I don't know if that had anything to do with it but I thought it was worth mentioning. Clear the cache and data/factory reset then install CM10 followed by Gapps that you installed on the SD earlier.
Once you boot up you should have the phone working but the keyboard will constantly flash a message that it can't run, don't worry about that right now. Now download a nightly version of CM10.1 located here:http://get.cm/?device=d2vzw&type=nightly
(I used cm-10.1-20121231-NIGHTLY-d2vzw.zip)
Now put this on your internal SD card as well and hold the power button for 2 seconds and press restart then select recovery. Now that you're back into the recovery menu CLEAR ONLY CACHE then install the new CM10.1 nightly you just put on your internal SD and then re-install Gapps 4.2.1 from before and reboot. This all worked for me and writing this message is the first thing I wanted to do afterward to make sure no one has to go through the frustration and heartache of constantly failing at installing the ROM they want. I hope this helps at least one person, if you have any questions I will try and answer them to the best of my knowledge but I'm fairly new to all of this.
Or you can just flash CM10.1 first and do this.......
Tap the 4 corners of the screen to bypass activation screen then go into settings> more> mobile networks> and change CDMA Subscription to RUIM/SIM and System Select to Automatic then reboot...
Click to expand...
Click to collapse
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Bosli said:
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Click to expand...
Click to collapse
Clear it's cache APPS > ALL > PHONE APP > Clear Cache.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
What are the correct settings?
I have been doing this a while... and I was already on the 10.0 stable build. So I flashed the 10.1 nightly... Now Play Store closes immediately after opening. I have tried to uninstall and install from .apk without success. CWRM opens and closes immediately , also uninstalled and reinstalled from .apk without success (You can get to it from booting to it with the phone off ). My Gmail app and account nowhere to be found. My attempt to go back to 10.0 were unsuccessful.
I've just installed a 14.1 nightly and tried to encrypt the device. Both times, it has hung at the "Encrypting..." screen post-reboot.
Initially, it displayed "Time remaining: 00:10", but this immediatly switched to "Time remaining: 00:00", with the progress bar still moving. It hangs like this for well over an hour.
Following a forced-reboot from the "Encrypting" screen, the phone asked for a password unlock -- I had set a 4x4 pattern, so could not complete (is there a way to convert from a 4x4 to a password? I know that this is possible with a 3x3).
Trying with a password leads to "Decryption unsuccessful - The password you entered is correct, but your data is corrupt ... do a factory reset "
I've factory-reset the device twice now, is there anything else I can try? Is this a known problem?
Recovery: twrp-3.0.2-0
edit: looks like there's a similar thread here: http://forum.xda-developers.com/oneplus-one/help/help-device-encryption-running-overnight-t3504125
I'm the author if the other thread. I ended up having to wipe. I needed encryption because I'm traveling soon, so I flashed back to CM13.
I tried all manber of things to get it working. Tried encrypting a fresh, clean install. I tried flagging CM13, encrypting, then flashing CM14 on the encrypted phone. But when I did that, the same "decryption unsuccessful" message appeared.
I gave up at that point, and was thankful that I had made a full backup of my titanium backup files in Dropbox.
Same issue here. I guess it's a bug. Hope it could be fixed soon.
I had exactly the same symptom on my HTC One M8 with AOKP (aokp_m8_nougat_nightly_2017-01-07) and CM14.1 (cm-14.1-20161225-NIGHTLY-m8).
I am now running CM12.1, where the problem doesn't occur. So it seems to be specific to Nougat somehow.
Recovery: twrp-3.0.2-0-m8
encryption works in tugapower
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
MAYDAY!
My phone keeps rebooting too.
Did you already fix it?
I downgraded & unlocked my note 4's bootloader (SM-N910V) using this process: https://forum.xda-developers.com/no...bilized-process-to-unlock-bootloader-t3375527
I checked for an EMMC BrickBug using the app, and it said I was good to go.
And yes, I did remove the SD card, both the one I used to unlock the bootloader, as well as the SD card I keep my ROMs on. The phone doesn't like to mount using TWRP all the time via USB.
It is the second time I have done the process, as the first time I encountered the same exact issues and went back to stock and upgraded as my brother requested. I did the exact same process before, and I got a bootloop on LineageOS, CyanogenMod, and a few random ROMs. The stock TouchWiz is terrible, this is attempt #2. Oddly enough, the bootloader did appear to re-lock itself when I upgraded, as I had to repeat the unlock process to get it to let me flash TWRP.
Before I installed LineageOS (https://forum.xda-developers.com/note-4-verizon/development/lineageos-t3557795) I first tried the default wipe, wiping Data, Cache and Dalvik. I then flashed the ROM. I got around 30min of the boot animation, and eventually it just shut off.
With CyanogenMod, I did the same process, and got around 4 hours of the boot animation, but no shutoff. That same thing happens with most other ROMs aside from Lineage.
I have also repeated the process with 3 ROMs, but advanced wiped Dalvik/ART Cache, system, data, cache and internal storage (only after attempting the first thing right after the bootloader unlock was done) and got the same result. I have no clue what the hell is going on with the device, and I couldn't find anything online.
I plan to try this rom: https://forum.xda-developers.com/note-4-verizon/development/rom-paulpizz-rom-t3360469 but I rather avoid stock based ROMs. The phone is at work, and I will attempt it tomorrow to see if it gets me anywhere - that'd be a bandaid as opposed to a fix though - if it does work.
Thanks
Alex_2259 said:
I downgraded & unlocked my note 4's bootloader (SM-N910V) using this process:...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2866810
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...
shmusername said:
Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...
shmusername said:
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...
Click to expand...
Click to collapse
Oh, you mean you want to recover your lost data. All I can say is try some data recovery software on PC, there isn't any guarantee that it will work though. Data recovery on android is not very reliable.
Sent from my LGL84VL using Tapatalk