Hello All,
Couple of days ago I decided to escape Samsung Knox while I still had the chance. So I flashed TWRP and a 4.3 GE ROM. Flashing went fine, but when I go to settings and try to enable device encryption, the phone just reboots back to lock screen as if nothing had happened. No problems what so ever after the reboot but no encryption either. With stock ROM encryption worked as expected and I decrypted the device before flashing anything.
Phone:
Hardware: Galaxy S4 GT-I9505 (originally a Samsung TW device running Knox-free I9505XXUBMGA)
ROM: Google Edition Android 4.3 | UNTOUCHED | JWR66Y.S003 | VERSION 2.0 (23/09)
Recovery: TWRP 2.6
How did I get here:
Brand new phone > Root > Encrypt > Regular use > Decrypt > TWRP > Wipe > GE ROM > No more encryption
What I have tried so far:
Googling & searching: Found some fellow victims and tried their suggestions but no help
Retried some 20 times at least
With and without USB connected
Portrait and landscape orientation
Reboot to safe mode
Reboot without SIM and MicroSD
Wipe and skip restore, thus no 3rd party apps installed
Wipe and re-flash
Wipe and flash different ROM: [AOSP]Official 4.3- S4 Google Edition- Finaly v2.0
Command line: vdc cryptfs enablecrypto inplace <password>
adb logcat: See below
All failed.
Here is some logs I managed to capture with adb logcat:
10-14 00:56:44.872 D/ActivityManager( 703): Trying to launch com.android.settings/.CryptKeeperConfirm$Blank
10-14 00:56:45.703 I/MountService( 703): encrypting storage...
10-14 00:56:45.703 D/VoldCmdListener( 225): cryptfs inplace {}
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /mnt/secure/staging
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /storage/extSdCard
10-14 00:56:47.355 I/CryptfsEE( 225): Just asked init to shut down class main
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt_1/sdcard_1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/container sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data/data1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/emulated sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data_1 sucessfully unmounted
10-14 00:56:47.835 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 19, action 1)
10-14 00:56:48.896 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 18, action 1)
10-14 00:56:49.997 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 17, action 1)
10-14 00:56:51.109 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 16, action 1)
10-14 00:56:52.210 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 15, action 1)
10-14 00:56:53.321 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 14, action 2)
10-14 00:56:54.412 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 13, action 2)
10-14 00:56:55.503 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 12, action 2)
10-14 00:56:56.594 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 11, action 2)
10-14 00:56:57.685 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 10, action 2)
10-14 00:56:58.766 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 9, action 2)
10-14 00:56:59.877 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 8, action 2)
10-14 00:57:00.958 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 7, action 2)
10-14 00:57:02.049 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 6, action 2)
10-14 00:57:03.150 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 5, action 2)
10-14 00:57:04.241 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 4, action 2)
10-14 00:57:05.332 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 3, action 2)
10-14 00:57:06.423 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 2, action 2)
10-14 00:57:07.505 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 1, action 2)
10-14 00:57:08.606 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 0, action 2)
10-14 00:57:09.697 E/CryptfsUT( 225): Giving up on unmount /data (Device or resource busy)
10-14 00:57:53.259 E/CryptfsEE( 225): Error (null) after framework is shutdown, no data changed, restarting system
Looks like failure on unmounting /data is the problem here but what's the root cause? And how get /data unmounted? I would greatly appreciate if someone could point me to right direction, or - even better - tell me what to do to get it fixed and my device encrypted again?
avah said:
Hello All,
Couple of days ago I decided to escape Samsung Knox while I still had the chance. So I flashed TWRP and a 4.3 GE ROM. Flashing went fine, but when I go to settings and try to enable device encryption, the phone just reboots back to lock screen as if nothing had happened. No problems what so ever after the reboot but no encryption either. With stock ROM encryption worked as expected and I decrypted the device before flashing anything.
Phone:
Hardware: Galaxy S4 GT-I9505 (originally a Samsung TW device running Knox-free I9505XXUBMGA)
ROM: Google Edition Android 4.3 | UNTOUCHED | JWR66Y.S003 | VERSION 2.0 (23/09)
Recovery: TWRP 2.6
How did I get here:
Brand new phone > Root > Encrypt > Regular use > Decrypt > TWRP > Wipe > GE ROM > No more encryption
What I have tried so far:
Googling & searching: Found some fellow victims and tried their suggestions but no help
Retried some 20 times at least
With and without USB connected
Portrait and landscape orientation
Reboot to safe mode
Reboot without SIM and MicroSD
Wipe and skip restore, thus no 3rd party apps installed
Wipe and re-flash
Wipe and flash different ROM: [AOSP]Official 4.3- S4 Google Edition- Finaly v2.0
Command line: vdc cryptfs enablecrypto inplace <password>
adb logcat: See below
All failed.
Here is some logs I managed to capture with adb logcat:
10-14 00:56:44.872 D/ActivityManager( 703): Trying to launch com.android.settings/.CryptKeeperConfirm$Blank
10-14 00:56:45.703 I/MountService( 703): encrypting storage...
10-14 00:56:45.703 D/VoldCmdListener( 225): cryptfs inplace {}
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /mnt/secure/staging
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /storage/extSdCard
10-14 00:56:47.355 I/CryptfsEE( 225): Just asked init to shut down class main
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt_1/sdcard_1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/container sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data/data1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/emulated sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data_1 sucessfully unmounted
10-14 00:56:47.835 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 19, action 1)
10-14 00:56:48.896 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 18, action 1)
10-14 00:56:49.997 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 17, action 1)
10-14 00:56:51.109 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 16, action 1)
10-14 00:56:52.210 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 15, action 1)
10-14 00:56:53.321 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 14, action 2)
10-14 00:56:54.412 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 13, action 2)
10-14 00:56:55.503 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 12, action 2)
10-14 00:56:56.594 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 11, action 2)
10-14 00:56:57.685 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 10, action 2)
10-14 00:56:58.766 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 9, action 2)
10-14 00:56:59.877 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 8, action 2)
10-14 00:57:00.958 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 7, action 2)
10-14 00:57:02.049 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 6, action 2)
10-14 00:57:03.150 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 5, action 2)
10-14 00:57:04.241 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 4, action 2)
10-14 00:57:05.332 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 3, action 2)
10-14 00:57:06.423 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 2, action 2)
10-14 00:57:07.505 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 1, action 2)
10-14 00:57:08.606 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 0, action 2)
10-14 00:57:09.697 E/CryptfsUT( 225): Giving up on unmount /data (Device or resource busy)
10-14 00:57:53.259 E/CryptfsEE( 225): Error (null) after framework is shutdown, no data changed, restarting system
Looks like failure on unmounting /data is the problem here but what's the root cause? And how get /data unmounted? I would greatly appreciate if someone could point me to right direction, or - even better - tell me what to do to get it fixed and my device encrypted again?
Click to expand...
Click to collapse
I'm having the exact same problem since 4.3 and found multiple articles offering suggestions about how to find services that might be holding /data open, but I have had no luck. Did you figure out a way to do this?
There is this...
http://code.google.com/p/android/issues/detail?id=58073
And I did the losf trick and the thing is that there are no open files, so what else could be holding the partition open?
Is there any other way to do encryption other than the UI or cryptofs?
thx1200 said:
I'm having the exact same problem since 4.3 and found multiple articles offering suggestions about how to find services that might be holding /data open, but I have had no luck. Did you figure out a way to do this?
There is this...
code.google.com/p/android/issues/detail?id=58073
And I did the losf trick and the thing is that there are no open files, so what else could be holding the partition open?
Is there any other way to do encryption other than the UI or cryptofs?
Click to expand...
Click to collapse
The issue is still present and I haven't managed to enable encryption. Haven't done much debugging either, though. I did try to run the command
Code:
while true; do echo; lsof | grep /data; sleep 0.2; done
as root while trying to encrypt the phone but it didn't reveal any open files (I added one echo command to separate consecutive iterations of the loop). This was expected since my earlier tests using safe mode and without 3rd party apps installed also failed.
Looks like it's not about open files but something much deeper in the system, like stale mount or something related to init process. Unfortunately that's way beyond my debugging skills.
Similar problem on Galaxy S3 with CF-AUTO-ROOT
I experience a very similar issue on my Galaxy S3 with cf-auto-root.
I also tried losf : no open files on /data.
Manual unmount works, but does not stop the error.
I notice in the log that other unmounts work (like data_1), but am surprised by the mentioned directories as some of them I don't recognize from the mount table.
The unmounting and encryption is handled by the vold service. I looked into the AOSP source code, but the messages are slightly different, so I suspect samsung is using a customized version (but it is not included in their open source code).
Frustrating... I need root, but also would like to have encryption...
Does anybody have android 4.3 + root + encryption working on Samsung?
Arjan Mels said:
I experience a very similar issue on my Galaxy S3 with cf-auto-root.
I also tried losf : no open files on /data.
Manual unmount works, but does not stop the error.
I notice in the log that other unmounts work (like data_1), but am surprised by the mentioned directories as some of them I don't recognize from the mount table.
The unmounting and encryption is handled by the vold service. I looked into the AOSP source code, but the messages are slightly different, so I suspect samsung is using a customized version (but it is not included in their open source code).
Frustrating... I need root, but also would like to have encryption...
Does anybody have android 4.3 + root + encryption working on Samsung?
Click to expand...
Click to collapse
Can confirm is not just limited to S4. Same issue with my Note 2 and are threads detailing inability to encrypt after root on S3 as well. Am monitoring threads for both and if I find something will post here too.
Reverting to stock firmware seems only way to enable encryption
chris19000 said:
Can confirm is not just limited to S4. Same issue with my Note 2 and are threads detailing inability to encrypt after root on S3 as well. Am monitoring threads for both and if I find something will post here too.
Click to expand...
Click to collapse
I also encountered this issue on the GT-i9505 after I rooted the phone. As described by OP when try to encrypt it reboots - start up fine - but there is no encryption. This is a big problem for me because it's a work phone, and I order to access work email and contacts list I need to comply with the Google Policy tool, and the company I work for set up the policy to require encryption (among other things such as complex password).
Once I installed stock firmware 4.3 I was able to encrypt, comply with the policy, and sync my work email and work contacts.
it seems do be really deep in android...
Because volks badadroid and Tigrouzen android images also have this issue...
Solved
I solved this issue on my Samsung Galaxy S4 2014 (P600).
I was able to encrypt the device after disabling SuperSU (which came with the auto-root rom) and rebooting.
Solved?
jsda said:
I solved this issue on my Samsung Galaxy S4 2014 (P600).
I was able to encrypt the device after disabling SuperSU (which came with the auto-root rom) and rebooting.
Click to expand...
Click to collapse
Sounds promising, but were you also able to enable root again after the encryption?
jsda said:
I solved this issue on my Samsung Galaxy S4 2014 (P600).
I was able to encrypt the device after disabling SuperSU (which came with the auto-root rom) and rebooting.
Click to expand...
Click to collapse
How did you disable SuperSU? I'm having the same problem on my Samsung Galaxy S3 (SGH-I747M on Rogers Canada, JB4.3). I tried disabling SuperSU by unchecking its Enable checkbox and rebooting. Did not solve the problem. Like an earlier commenter, I also did not find anything suspicious with lsof. Also tried disabling Wi-Fi (as suggested in a Twitter post I came across) to no avail.
Maybe Encryption was considered as a bloatware and been removed
Sent from dish washer
Ok, gave this one more try but still no luck. What I tried was to use the stock ROM mentioned in the OP for encryption then install TWRP on the already encrypted phone and then install a custom ROM again. The theory behind this approach is that encryption is a block level operation that happens below the file system and the encryption keys are stored at the very end of the volume on an unallocated area. Thus everything happens outside the file system and as long as you don't re-partition the drive, keys and encryption in general should stay intact even after complete wipe. I also had read rumors that some versions of TWRP should be encryption aware and be able to mount encrypted volumes. So I wiped, re-flashed stock ROM with Odin, preformed factory reset, rooted with CF-Auto-Root and encrypted the phone without any problems (except that not-so-minor fact that I was back with stock 4.2.2 TW phone.)
Then I flashed TWRP and tried to continue with custom ROM installation but this was the point where I learned that rumors about TWRP's encryption supports are just rumors. It doesn't work. At least not with the implementation used on stock I9505 and of course YMMV. Booting to recovery works and upon booting TWRP – depending on the version – even prompted for the password but then it claimed that my password was incorrect and /data wasn’t mounted. I had chosen a very simple password (Password123) because I didn't know what kind of UI and keyboard TWRP's password entry screen was going to have and I also tried several times, so typos were ruled out. No matter what did, my password wasn’t accepted in TWRP. Different versions didn't help either. Tried first with TWRP 2.6.3.1 then 2.6.1.0 and finally 2.6.0.0. All failed and TWRP 2.6.3.1 didn't even ask for the password. Meanwhile booting to OS worked fine with the same password.
At this point I decided that due to all the sensitive data – like work stuff, call recordings, etc. – I have stored in my phone, the encryption is more important than custom ROM. So I flashed back to stock (*sigh*) for good. Now I'm back in square one but at least I have an encrypted phone and I can use my SIM card PIN code again
DeviceEnryption with JB 4.3
I have an S3 but with same error
"....Failed to unmount /data (Device or resource busy, retries 19, action 1).."
With OmegaROMv54.
There are different solutions to overcome this error.
For me at the end altough a different phone, the solution stated in "https://code.google.com/p/android/issues/detail?id=58073 worked
#43 .. @gmail.com
I believe there is an issue with the power logic allowing it to start.
Do:
Start>Security>Encrypt Phone
Enter your PIN.
JUST BEFORE you press 'encrypt phone' to start the reboot process, unplug your USB, then press 'encrypt phone'.
You should be OK now.
"
avah said:
Hello All,
Couple of days ago I decided to escape Samsung Knox while I still had the chance. So I flashed TWRP and a 4.3 GE ROM. Flashing went fine, but when I go to settings and try to enable device encryption, the phone just reboots back to lock screen as if nothing had happened. No problems what so ever after the reboot but no encryption either. With stock ROM encryption worked as expected and I decrypted the device before flashing anything.
Phone:
Hardware: Galaxy S4 GT-I9505 (originally a Samsung TW device running Knox-free I9505XXUBMGA)
ROM: Google Edition Android 4.3 | UNTOUCHED | JWR66Y.S003 | VERSION 2.0 (23/09)
Recovery: TWRP 2.6
How did I get here:
Brand new phone > Root > Encrypt > Regular use > Decrypt > TWRP > Wipe > GE ROM > No more encryption
What I have tried so far:
Googling & searching: Found some fellow victims and tried their suggestions but no help
Retried some 20 times at least
With and without USB connected
Portrait and landscape orientation
Reboot to safe mode
Reboot without SIM and MicroSD
Wipe and skip restore, thus no 3rd party apps installed
Wipe and re-flash
Wipe and flash different ROM: [AOSP]Official 4.3- S4 Google Edition- Finaly v2.0
Command line: vdc cryptfs enablecrypto inplace <password>
adb logcat: See below
All failed.
Here is some logs I managed to capture with adb logcat:
10-14 00:56:44.872 D/ActivityManager( 703): Trying to launch com.android.settings/.CryptKeeperConfirm$Blank
10-14 00:56:45.703 I/MountService( 703): encrypting storage...
10-14 00:56:45.703 D/VoldCmdListener( 225): cryptfs inplace {}
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /mnt/secure/staging
10-14 00:56:45.753 E/Vold ( 225): unmountEcryptFs not mounted /storage/extSdCard
10-14 00:56:47.355 I/CryptfsEE( 225): Just asked init to shut down class main
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt_1/sdcard_1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/container sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data/data1 sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /mnt/shell/emulated sucessfully unmounted
10-14 00:56:47.835 I/CryptfsUT( 225): /data_1 sucessfully unmounted
10-14 00:56:47.835 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 19, action 1)
10-14 00:56:48.896 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 18, action 1)
10-14 00:56:49.997 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 17, action 1)
10-14 00:56:51.109 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 16, action 1)
10-14 00:56:52.210 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 15, action 1)
10-14 00:56:53.321 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 14, action 2)
10-14 00:56:54.412 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 13, action 2)
10-14 00:56:55.503 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 12, action 2)
10-14 00:56:56.594 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 11, action 2)
10-14 00:56:57.685 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 10, action 2)
10-14 00:56:58.766 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 9, action 2)
10-14 00:56:59.877 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 8, action 2)
10-14 00:57:00.958 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 7, action 2)
10-14 00:57:02.049 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 6, action 2)
10-14 00:57:03.150 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 5, action 2)
10-14 00:57:04.241 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 4, action 2)
10-14 00:57:05.332 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 3, action 2)
10-14 00:57:06.423 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 2, action 2)
10-14 00:57:07.505 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 1, action 2)
10-14 00:57:08.606 W/CryptfsUT( 225): Failed to unmount /data (Device or resource busy, retries 0, action 2)
10-14 00:57:09.697 E/CryptfsUT( 225): Giving up on unmount /data (Device or resource busy)
10-14 00:57:53.259 E/CryptfsEE( 225): Error (null) after framework is shutdown, no data changed, restarting system
Looks like failure on unmounting /data is the problem here but what's the root cause? And how get /data unmounted? I would greatly appreciate if someone could point me to right direction, or - even better - tell me what to do to get it fixed and my device encrypted again?
Click to expand...
Click to collapse
xdascrat said:
I have an S3 but with same error
"....Failed to unmount /data (Device or resource busy, retries 19, action 1).."
With OmegaROMv54.
There are different solutions to overcome this error.
For me at the end altough a different phone, the solution stated in "https://code.google.com/p/android/issues/detail?id=58073 worked
#43 .. @gmail.com
I believe there is an issue with the power logic allowing it to start.
Do:
Start>Security>Encrypt Phone
Enter your PIN.
JUST BEFORE you press 'encrypt phone' to start the reboot process, unplug your USB, then press 'encrypt phone'.
You should be OK now.
"
Click to expand...
Click to collapse
It's not about power logic. You can bypass the battery level and charging tests by initating the encryption directly from the command line. Just say "vdc cryptfs enablecrypto inplace your_max_16_char_password_here" as root. But the encryption will still fail.
And yes, I have tested also this unplug-your-usb-calbe trick mentioned above. And no, I it didn't help.
Some details:
In my case entering the command "vdc cryptfs enablecrypto inplace" in terminal just doesn't work although repeated many times.
In adb logcat it was also trying to unmount /data many times, but failed.
I disabled many services, tried killing processes with a taskkiller short before performing the above command, as suggested in
code .google. com/p/android/issues/detail?id=58073#c48
But still umounting /data keeps on failing.
After that I enabled all services again,, rebooted, no more taskkilling, doing that USB Cable unplugging , and encryption worked. I hope, this issue will be fixed soon.
I also ran into this problem after I did a manual update to 4.3 on my Galaxy S3 via Kies. I then decrypted the device, rooted it and wanted to encrypt again.
I finally got it into starting the encryption (currently 30%, fingers crossed) via:
1. Disabling SuperSU (app-manager), though I don't think that this is really needed as disabling alone didn't work
2. Unmounting everything that I could using adb shell
- everything under /mn/asec
- /mnt/asec itself
- every bind-mount from /data/ to some legacy folders
So, finally I had only the following left:
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
After that I started the command from the shell via vdc cryptfs enablecrypto inplace <password>
Maybe this helps others.
Best regards,
Maz
EDIT: Encryption finished and is working!
I think I've got a fix!
I think I've found a way to do this!
I was having the same problem, press encrypt (or run the terminal command) and the phone would just reboot, still not encrypted.
I tried to unmount /data without luck, I tried airplane mode, I tried force-quitting and turing off as many services and apps as I could find, no luck.
Then I tried SAFE MODE. So if you LONG PRESS the power off button you'll get a window that pops up and asks...
Reboot to Safe Mode
Do you want to reboot into safe mode? This will disable all third party applications you have installed. They will be restored when you reboot again. Ok/Cancel.
Click to expand...
Click to collapse
So I rebooted into safe mode, went through the normal settings menu to engage encryption (did not have access to terminal anymore since all the apps were locked out) and now it's going strong.
So, to sum up, rebooting into safe mode may allow you to encrypt your device when it is otherwise failing. Enjoy.
ncotton said:
So, to sum up, rebooting into safe mode may allow you to encrypt your device when it is otherwise failing. Enjoy.
Click to expand...
Click to collapse
Glad to hear that booting into safe mode helped you. Safe mode is a lesser-known feature of Android and always worth a try when there is something weird going on (or not going on!) on the device. Unfortunately I had already tested that with no luck. As I wrote in my earlier posts, all these methods have failed:
avah said:
What I have tried so far:
Googling & searching: Found some fellow victims and tried their suggestions but no help
Retried some 20 times at least
With and without USB connected
Portrait and landscape orientation
Reboot to safe mode
Reboot without SIM and MicroSD
Wipe and skip restore, thus no 3rd party apps installed
Wipe and re-flash
Wipe and flash different ROM: [AOSP]Official 4.3- S4 Google Edition- Finaly v2.0
Command line: vdc cryptfs enablecrypto inplace <password>
...
Click to expand...
Click to collapse
Thanks for the suggestion anyway!
A slightly different issue
This is what keeps my encryption from starting (using vdc from the command line of ADB):
E/ProcessKiller( 1961): [email protected] tmp-mksh (6996) has open file /data/data/eu.chainfire.supersu/logs/L13935954020000.GRANTED.ADB shell (deleted)
W/ProcessKiller( 1961): [email protected] SIGHUP to process 6996
D/ProcessKiller( 1961): Wait for death /proc/6996
W/CryptfsUT( 1961): Failed to unmount /data (Device or resource busy, retries 18, action 1)
...
W/CryptfsUT( 1961): Failed to unmount /data (Device or resource busy, retries 0, action 2)
E/CryptfsUT( 1961): Giving up on unmount /data (Device or resource busy)
And after disabling the supersu logging feature:
I did unmount /data and it did not complain about anything:
# umount /data
umount /data
then started encryption:
vdc cryptfs enablecrypto inplace whatever_password
and this is the log:
I/CryptfsUT( 1962): /mnt_1/sdcard_1 sucessfully unmounted
I/CryptfsUT( 1962): /mnt/shell/container sucessfully unmounted
I/CryptfsUT( 1962): /data/data1 sucessfully unmounted
I/CryptfsUT( 1962): /storage/PersonalPage sucessfully unmounted
I/CryptfsUT( 1962): /mnt/shell/personalpage sucessfully unmounted
I/CryptfsUT( 1962): /mnt/shell/emulated sucessfully unmounted
I/CryptfsUT( 1962): /data_1 sucessfully unmounted
W/CryptfsUT( 1962): Failed to unmount /data (Device or resource busy, retries 19, action 1)
...
W/CryptfsUT( 1962): Failed to unmount /data (Device or resource busy, retries 0, action 2)
E/CryptfsUT( 1962): Giving up on unmount /data (Device or resource busy)
I/dumpstate( 7205): begin
I/dumpstate( 7205): done
E/CryptfsEE( 1962): Error (null) after framework is shutdown, no data changed, restarting system
Still nothing...
I had huge problems getting encryption to work after stock 4.4 + cf_auto_root with the logcat telling me /data was busy. What finally did it was to boot in Safe Mode (hold volume down during boot), over adb shell unmounting everything down to and including /data manually and then issuing a vdc cryptfs enablecrypto. This way I can now also enjoy pin lockscreen and device encryption while on stock rom.
hi everyone!
so some of my friends told me that they cannot call me, like im switched off, so i started testing and it turns out that whenever someone tries to call me, i get the error message com.android.phone stopped working.
EDIT: i can receive calls with private numbers, just not the ones with visible numbers.
i know the best solution would be a data wipe, but i really just cant afford the time and effort to set my phone up again the way it is right now, so i would love another solution.
didnt find much help either here on xda or other forums, so thats why i thought id start a new thread.
i tried clearing system-wide cache, dalvik cache, cache and data of com.android.phone (via deleting the content of /data/data/com.android.phone), sim toolkit (read somewhere that it might help), and the dialer, but the issue remains.
tried replacing the apk in /system/app from the cm11 m7 zip, reinstalling the whole system again, fixing permissions, etc., no success.
im on cm11 m7 right now with a modified CAF franco kernel (i've been using this combo for more than a month, the kernel for a few months, and did not have such issue).
i did not change or install or whatever anything before/when/after i noticed the issue.
i extracted the logcat where the issue happened:
Code:
07-16 17:08:17.085 E/auditd (184): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:21.981 E/auditd (564): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:27.236 E/auditd (688): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:32.762 E/auditd (713): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:37.047 E/auditd (759): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:42.202 E/auditd (1185): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:47.238 E/auditd (1718): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:49.541 I/BootReceiver(567): Checking for fsck errors
07-16 17:08:51.513 E/auditd (1991): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:56.488 E/auditd (2271): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:00.687 E/auditd (2427): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:05.692 E/auditd (2582): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:10.707 E/auditd (2625): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:15.723 E/auditd (2762): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:20.738 E/auditd (2867): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:25.743 E/auditd (3119): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:30.759 E/auditd (3263): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:35.764 E/auditd (3381): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:40.780 E/auditd (3565): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:42.622 I/dalvikvm(3569): Could not find method android.speech.tts.SynthesisCallback.error, referenced from method com.google.android.tts.local.LocalSynthesizer.onSynthesizeV2
07-16 17:09:42.622 W/dalvikvm(3569): VFY: unable to resolve interface method 428: Landroid/speech/tts/SynthesisCallback;.error (I)V
07-16 17:09:42.622 I/dalvikvm(3569): Could not find method android.speech.tts.SynthesisCallback.error, referenced from method com.google.android.tts.local.LocalSynthesizer.onSynthesizeV2
07-16 17:09:42.622 W/dalvikvm(3569): VFY: unable to resolve interface method 428: Landroid/speech/tts/SynthesisCallback;.error (I)V
07-16 17:09:43.002 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.012 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.022 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.022 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.042 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.042 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:45.795 E/auditd (3700): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:46.536 D/GCMBaseIntentService(3681): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:09:50.800 E/auditd (3784): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:54.364 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.374 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.384 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.384 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.394 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.394 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:55.816 E/auditd (3852): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:00.831 E/auditd (3928): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:03.414 D/GCMBaseIntentService(3935): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:10:09.520 E/auditd (4055): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:32.410 D/GCMBaseIntentService(3935): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:10:32.420 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:10:33.321 E/auditd (4147): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:33.682 D/ACRA (4154): Looking for error files in /data/data/pl.solidexplorer/files
07-16 17:10:33.682 D/ACRA (4154): Looking for error files in /data/data/pl.solidexplorer/files
07-16 17:10:38.337 E/auditd (4226): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:43.352 E/auditd (4240): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:48.357 E/auditd (4251): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:53.373 E/auditd (4264): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:58.378 E/auditd (4270): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:03.413 E/auditd (4290): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:08.429 E/auditd (4296): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:12.613 E/cutils-trace(4311): Error opening trace file: No such file or directory (2)
07-16 17:11:13.454 E/auditd (4341): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:18.459 E/auditd (4349): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:23.475 E/auditd (4362): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:28.490 E/auditd (4371): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:33.506 E/auditd (4378): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:37.650 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:11:38.511 E/auditd (4396): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:43.526 E/auditd (4418): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:48.532 E/auditd (4431): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:53.537 E/auditd (4440): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:58.552 E/auditd (4450): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:03.558 E/auditd (4476): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:08.563 E/auditd (4491): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:13.568 E/auditd (4501): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:18.584 E/auditd (4508): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:23.589 E/auditd (4519): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:28.604 E/auditd (4537): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:33.610 E/auditd (4572): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:38.615 E/auditd (4593): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:43.270 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:12:43.620 E/auditd (4631): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:48.476 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:12:48.646 E/auditd (4700): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:53.651 E/auditd (4723): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:58.656 E/auditd (4756): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:03.662 E/auditd (4775): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:08.687 E/auditd (4779): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:13.692 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:13:13.702 E/auditd (4796): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:18.728 E/auditd (4806): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:23.753 E/auditd (4813): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:28.769 E/auditd (4820): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:33.794 E/auditd (4824): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:38.809 E/auditd (4827): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:43.845 E/auditd (4832): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:47.709 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:13:48.700 E/auditd (4975): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:53.625 E/auditd (5002): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:58.117 E/auditd (5108): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:03.133 E/auditd (5128): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:08.148 E/auditd (5131): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:13.163 E/auditd (5139): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:18.189 E/auditd (5146): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:23.204 E/auditd (5149): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:28.209 E/auditd (5154): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:33.225 E/auditd (5167): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:38.230 E/auditd (5183): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:43.245 E/auditd (5191): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:48.261 E/auditd (5200): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:18.280 E/auditd (5219): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:40.280 E/auditd (5252): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:45.296 E/auditd (5296): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:45.656 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:15:49.190 E/cutils-trace(5501): Error opening trace file: No such file or directory (2)
07-16 17:15:50.021 E/auditd (5531): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:50.361 E/cutils-trace(5530): Error opening trace file: No such file or directory (2)
07-16 17:15:50.771 E/cutils-trace(5551): Error opening trace file: No such file or directory (2)
07-16 17:15:51.112 E/cutils-trace(5570): Error opening trace file: No such file or directory (2)
07-16 17:15:51.392 E/cutils-trace(5584): Error opening trace file: No such file or directory (2)
07-16 17:15:51.412 E/cutils-trace(5591): Error opening trace file: No such file or directory (2)
07-16 17:15:55.997 E/auditd (5634): Failed on audit_set_pid with error: Protocol not supported
07-16 17:16:00.001 E/auditd (5642): Failed on audit_set_pid with error: Protocol not supported
does anyone have any idea what i could do here?
i would be grateful for any help!
zakoo2 said:
hi everyone!
so some of my friends told me that they cannot call me, like im switched off, so i started testing and it turns out that whenever someone tries to call me, i get the error message com.android.phone stopped working.
i know the best solution would be a data wipe, but i really just cant afford the time and effort to set my phone up again the way it is right now, so i would love another solution.
didnt find much help either here on xda or other forums, so thats why i thought id start a new thread.
i tried clearing system-wide cache, dalvik cache, cache and data of com.android.phone (via deleting the content of /data/data/com.android.phone), sim toolkit (read somewhere that it might help), and the dialer, but the issue remains.
tried replacing the apk in /system/app from the cm11 m7 zip, reinstalling the whole system again, fixing permissions, etc., no success.
im on cm11 m7 right now with a modified CAF franco kernel (i've been using this combo for more than a month, the kernel for a few months, and did not have such issue).
i did not change or install or whatever anything before/when/after i noticed the issue.
i extracted the logcat where the issue happened:
Code:
07-16 17:08:17.085 E/auditd (184): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:21.981 E/auditd (564): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:27.236 E/auditd (688): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:32.762 E/auditd (713): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:37.047 E/auditd (759): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:42.202 E/auditd (1185): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:47.238 E/auditd (1718): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:49.541 I/BootReceiver(567): Checking for fsck errors
07-16 17:08:51.513 E/auditd (1991): Failed on audit_set_pid with error: Protocol not supported
07-16 17:08:56.488 E/auditd (2271): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:00.687 E/auditd (2427): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:05.692 E/auditd (2582): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:10.707 E/auditd (2625): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:15.723 E/auditd (2762): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:20.738 E/auditd (2867): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:25.743 E/auditd (3119): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:30.759 E/auditd (3263): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:35.764 E/auditd (3381): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:40.780 E/auditd (3565): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:42.622 I/dalvikvm(3569): Could not find method android.speech.tts.SynthesisCallback.error, referenced from method com.google.android.tts.local.LocalSynthesizer.onSynthesizeV2
07-16 17:09:42.622 W/dalvikvm(3569): VFY: unable to resolve interface method 428: Landroid/speech/tts/SynthesisCallback;.error (I)V
07-16 17:09:42.622 I/dalvikvm(3569): Could not find method android.speech.tts.SynthesisCallback.error, referenced from method com.google.android.tts.local.LocalSynthesizer.onSynthesizeV2
07-16 17:09:42.622 W/dalvikvm(3569): VFY: unable to resolve interface method 428: Landroid/speech/tts/SynthesisCallback;.error (I)V
07-16 17:09:43.002 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.012 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.022 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.022 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.042 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:43.042 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:45.795 E/auditd (3700): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:46.536 D/GCMBaseIntentService(3681): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:09:50.800 E/auditd (3784): Failed on audit_set_pid with error: Protocol not supported
07-16 17:09:54.364 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.374 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.384 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.384 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.394 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:54.394 E/Parcel (567): Caused by: java.lang.NoClassDefFoundError: com/anydo/cal/objects/CalendarAlert
07-16 17:09:55.816 E/auditd (3852): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:00.831 E/auditd (3928): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:03.414 D/GCMBaseIntentService(3935): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:10:09.520 E/auditd (4055): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:32.410 D/GCMBaseIntentService(3935): handleRegistration: registrationId = APA91bH915cxcypstoqWgs2kWY9t2N-FugLVgXV69ZKcqYkh8flcTiS2Fq6pWHUKz6qPbYig3wN1N9luMrmo01CJah_62BvwiZ2goXpvHm-89rfSzZ7y57Wb6jaNceqPg6hCn3-JFpsjEOY7dE599NAqBZsSyE8EBA, error = null, unregistered = null
07-16 17:10:32.420 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:10:33.321 E/auditd (4147): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:33.682 D/ACRA (4154): Looking for error files in /data/data/pl.solidexplorer/files
07-16 17:10:33.682 D/ACRA (4154): Looking for error files in /data/data/pl.solidexplorer/files
07-16 17:10:38.337 E/auditd (4226): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:43.352 E/auditd (4240): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:48.357 E/auditd (4251): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:53.373 E/auditd (4264): Failed on audit_set_pid with error: Protocol not supported
07-16 17:10:58.378 E/auditd (4270): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:03.413 E/auditd (4290): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:08.429 E/auditd (4296): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:12.613 E/cutils-trace(4311): Error opening trace file: No such file or directory (2)
07-16 17:11:13.454 E/auditd (4341): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:18.459 E/auditd (4349): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:23.475 E/auditd (4362): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:28.490 E/auditd (4371): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:33.506 E/auditd (4378): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:37.650 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:11:38.511 E/auditd (4396): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:43.526 E/auditd (4418): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:48.532 E/auditd (4431): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:53.537 E/auditd (4440): Failed on audit_set_pid with error: Protocol not supported
07-16 17:11:58.552 E/auditd (4450): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:03.558 E/auditd (4476): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:08.563 E/auditd (4491): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:13.568 E/auditd (4501): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:18.584 E/auditd (4508): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:23.589 E/auditd (4519): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:28.604 E/auditd (4537): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:33.610 E/auditd (4572): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:38.615 E/auditd (4593): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:43.270 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:12:43.620 E/auditd (4631): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:48.476 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:12:48.646 E/auditd (4700): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:53.651 E/auditd (4723): Failed on audit_set_pid with error: Protocol not supported
07-16 17:12:58.656 E/auditd (4756): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:03.662 E/auditd (4775): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:08.687 E/auditd (4779): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:13.692 E/ACDB-LOADER(191): Error: ACDB AudProc vol returned = -8
07-16 17:13:13.702 E/auditd (4796): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:18.728 E/auditd (4806): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:23.753 E/auditd (4813): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:28.769 E/auditd (4820): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:33.794 E/auditd (4824): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:38.809 E/auditd (4827): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:43.845 E/auditd (4832): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:47.709 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:13:48.700 E/auditd (4975): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:53.625 E/auditd (5002): Failed on audit_set_pid with error: Protocol not supported
07-16 17:13:58.117 E/auditd (5108): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:03.133 E/auditd (5128): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:08.148 E/auditd (5131): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:13.163 E/auditd (5139): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:18.189 E/auditd (5146): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:23.204 E/auditd (5149): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:28.209 E/auditd (5154): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:33.225 E/auditd (5167): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:38.230 E/auditd (5183): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:43.245 E/auditd (5191): Failed on audit_set_pid with error: Protocol not supported
07-16 17:14:48.261 E/auditd (5200): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:18.280 E/auditd (5219): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:40.280 E/auditd (5252): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:45.296 E/auditd (5296): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:45.656 E/LocSvc_eng(567): W/int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float): log_eng state error: instance not initialized
07-16 17:15:49.190 E/cutils-trace(5501): Error opening trace file: No such file or directory (2)
07-16 17:15:50.021 E/auditd (5531): Failed on audit_set_pid with error: Protocol not supported
07-16 17:15:50.361 E/cutils-trace(5530): Error opening trace file: No such file or directory (2)
07-16 17:15:50.771 E/cutils-trace(5551): Error opening trace file: No such file or directory (2)
07-16 17:15:51.112 E/cutils-trace(5570): Error opening trace file: No such file or directory (2)
07-16 17:15:51.392 E/cutils-trace(5584): Error opening trace file: No such file or directory (2)
07-16 17:15:51.412 E/cutils-trace(5591): Error opening trace file: No such file or directory (2)
07-16 17:15:55.997 E/auditd (5634): Failed on audit_set_pid with error: Protocol not supported
07-16 17:16:00.001 E/auditd (5642): Failed on audit_set_pid with error: Protocol not supported
does anyone have any idea what i could do here?
i would be grateful for any help!
Click to expand...
Click to collapse
I had some issues with my dialer app as well. I flashed the CM11 dialer from N5XP and it's been working without any problems. http://n5x.mobi/n4
unfortunately the same issue persists after flashing the new dialer zip. but thanks!
Sent from my Nexus 4 using XDA Premium 4 mobile app
How about updating to cm11 m8 with its stock kernel? I bet this is caused by your kernel...
CCody said:
How about updating to cm11 m8 with its stock kernel? I bet this is caused by your kernel...
Click to expand...
Click to collapse
i tried installing only the rom and not the kernel (m7, m8 was a bit instable for me), but i still got the problem.
and i edited the first post:
i can receive calls from unknown / private numbers. i get more and more confused by this...
I think you should do a full wipe and a clean flash afterwards. Just make a back up from your apps + data und you are good to go.
CCody said:
I think you should do a full wipe and a clean flash afterwards. Just make a back up from your apps + data und you are good to go.
Click to expand...
Click to collapse
could you please recommend a good app/data backup tool? i already tried titanium and helium in the past, but neither could save every app and every appdata and settings.
zakoo2 said:
could you please recommend a good app/data backup tool? i already tried titanium and helium in the past, but neither could save every app and every appdata and settings.
Click to expand...
Click to collapse
I dont have any good experience with back up apps. Those didnt work like I wanted to. I always do a back up via adb. You just need to have root and back up everything with command lines. When you arent familiar with such things, then I recommand you to use WugFreshs Nexus Toolkit. It helps a lot.
If there are more questions please dont mind to ask. I dont want you to do a false step and lose all your data.
CCody said:
I dont have any good experience with back up apps. Those didnt work like I wanted to. I always do a back up via adb. You just need to have root and back up everything with command lines. When you arent familiar with such things, then I recommand you to use WugFreshs Nexus Toolkit. It helps a lot.
If there are more questions please dont mind to ask. I dont want you to do a false step and lose all your data.
Click to expand...
Click to collapse
thank you, using wugfreshs toolkit might actually be the best mode of backup i will get back to you as soon as i get to try it.
zakoo2 said:
thank you, using wugfreshs toolkit might actually be the best mode of backup i will get back to you as soon as i get to try it.
Click to expand...
Click to collapse
Any time [emoji106][emoji6]
CCody said:
Any time [emoji106][emoji6]
Click to expand...
Click to collapse
i couldnt backup only data and apps with wugfresh, so i ended up simply installing android l preview, and im running it since.
although i do miss cm features like profiles and the customizable notification led (i know, lightflow is a good alternative, but i had wakelock and drain troubles with it in the past).