I'm sorry. I'm a noob and trying my best, but am confused. I unlocked bootloader, flashed TWRP and then SuperSU. I'm able to root my phone, but whenever I go into TWRP, it says the phone is encrypted. I understand that without it the radio won't work. Is there a way around that? I keep people talking about s-off. If I use Sunshine to s-off, will it decrypt my phone and allow the radio to work???
Showing posts with label encryption. Show all posts
Showing posts with label encryption. Show all posts
Thursday, 28 July 2016
Wednesday, 27 July 2016
Questions about encryption of an unlocked OP3
Hey Guys,
When I got my OP3 I unlocked the bootloader right away and installed FreedomOS to get rid of the bloatware. As this is my first device, which comes with a locked bootloader and decryption, I have some questions about this topic. I was wondering that the encryption does not make any sense when you unlock your bootloader, because if somebody steals your phone, he can just enter twrp and access all your data. Then I flashed CM and after that TWRP was asking me to set a pin or pattern to lock my phone. Now I've to unlock my phone every time I want to enter the recovery or boot the system with a pattern, which is great, because now the encryption is not worthless anymore. Now I'm asking myself if this feature is somehow integrated into CM or was it just random that I found this feature? Is there any way to get this also with OOS installed? What things do I have to note to not accidentally make my phone unencryptable with the pattern? Is this even possible, maybe by flashing a new recovery or so?
Thanks in advance
When I got my OP3 I unlocked the bootloader right away and installed FreedomOS to get rid of the bloatware. As this is my first device, which comes with a locked bootloader and decryption, I have some questions about this topic. I was wondering that the encryption does not make any sense when you unlock your bootloader, because if somebody steals your phone, he can just enter twrp and access all your data. Then I flashed CM and after that TWRP was asking me to set a pin or pattern to lock my phone. Now I've to unlock my phone every time I want to enter the recovery or boot the system with a pattern, which is great, because now the encryption is not worthless anymore. Now I'm asking myself if this feature is somehow integrated into CM or was it just random that I found this feature? Is there any way to get this also with OOS installed? What things do I have to note to not accidentally make my phone unencryptable with the pattern? Is this even possible, maybe by flashing a new recovery or so?
Thanks in advance
Monday, 25 July 2016
CM12.1 Encryption locked me out of my fire. What now?
In short: CM offers me a 3x3 matrix to unlock my device but my pattern needs a 4x4 matrix.
Hi, I previously installed CM12.1 on it following a video (the old FireOS version was 5.0.1) from rootjunky.
Yesterday I tried to encrypt it via the option in settings. Now asks me to enter my pattern to start Android and it displays a 3x3 dot matrix but my pattern needs a 4x4 matrix. Thus I can no longer access it. The data on the tablet is irrelevant and can be wiped if necessary. What should I do? Should I a factory reset?
Maybe I am using the wrong keywords but I haven't yet found a helpful forum post.
Please help. Thank you!
regards
Axel
Hi, I previously installed CM12.1 on it following a video (the old FireOS version was 5.0.1) from rootjunky.
Yesterday I tried to encrypt it via the option in settings. Now asks me to enter my pattern to start Android and it displays a 3x3 dot matrix but my pattern needs a 4x4 matrix. Thus I can no longer access it. The data on the tablet is irrelevant and can be wiped if necessary. What should I do? Should I a factory reset?
Maybe I am using the wrong keywords but I haven't yet found a helpful forum post.
Please help. Thank you!
regards
Axel
Friday, 22 July 2016
Encryption never starts, stays at boot animation.
Hey there!
For security purposes, I'd like to encrypt the data on my Nexus 6P. However, the encryption process fails to start. My phone goes into the boot animation, and it stays there permanently. Interrupting the process does not result in data loss: the phone reboots just fine, all my data is accessible, and it runs good as new. What this tells me is that something is preventing the encryption process from starting in the first place. My problem is that I am not particularly well versed in these matters, and I'm at a loss for how to proceed.
I have made a full Nandroid backup and saved it on my PC, so I'm willing to do some experimenting if there's no easy solution.
I am running the MTC19X build of stock Android. I've made two significant modifications: SuperSU systemless root, and systemless Xposed. In terms of other weird stuff, I have AdAway (from F-Droid) running.
Things I've attempted which did not solve the problem:
One interesting idea comes from a Nexus support thread (which I can't link because this is my first post), which suggests that some app or another could be holding files open and preventing the process from starting. I'm not sure what could be doing that, aside from Xposed or other root-related stuff, but I feel I covered that by disabling root on my last attempt. If anyone has any ideas on this front, though, I'm all ears.
I also took the liberty of running ADB's logcat feature, which suggests that the "data is busy" hypothesis is correct:
Looking these over makes me think the BOINC app might be the problem, so I figured I'd uninstall it and try again. I'm watching the boot animation right now; wish me luck!
Anyway, if anyone else has any other ideas (especially after reading those logs, I'm not at all an expert on these matters so I definitely don't completely know what I'm looking at), I'm all ears.
Thank you all for your time.
For security purposes, I'd like to encrypt the data on my Nexus 6P. However, the encryption process fails to start. My phone goes into the boot animation, and it stays there permanently. Interrupting the process does not result in data loss: the phone reboots just fine, all my data is accessible, and it runs good as new. What this tells me is that something is preventing the encryption process from starting in the first place. My problem is that I am not particularly well versed in these matters, and I'm at a loss for how to proceed.
I have made a full Nandroid backup and saved it on my PC, so I'm willing to do some experimenting if there's no easy solution.
I am running the MTC19X build of stock Android. I've made two significant modifications: SuperSU systemless root, and systemless Xposed. In terms of other weird stuff, I have AdAway (from F-Droid) running.
Things I've attempted which did not solve the problem:
- Starrted encryption process, left running overnight. No joy. I'm fairly sure it's not just me being impatient, but I'm open to just leaving the thing plugged in for 24 hours to see if that works.
- Disabled Xposed Framework and used SuperSU app to disable root. Tried again, nothing changed. Open to trying again by fully uninstalling these and seeing what happens, but would prefer not to re-root and set up from scratch again.
- Inspired by a solution that worked for a similar problem on my old Moto G, I reduced the size of the /data partition by a small amount, leaving a small amount of unallocated space on my device. (On the Moto G, this solved a problem where Android had no place to put certain data relating to the encrypted files.) Worked with the Moto, but no such luck this time. Could go in and reverse this change if necessary, or reduce the size of the partition even more.
One interesting idea comes from a Nexus support thread (which I can't link because this is my first post), which suggests that some app or another could be holding files open and preventing the process from starting. I'm not sure what could be doing that, aside from Xposed or other root-related stuff, but I feel I covered that by disabling root on my last attempt. If anyone has any ideas on this front, though, I'm all ears.
I also took the liberty of running ADB's logcat feature, which suggests that the "data is busy" hypothesis is correct:
Code:
07-21 23:30:02.845 7604 7604 W boinc : type=1400 audit(0.0:6477): avc: denied { search } for name="1" dev="proc" ino=50414 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
07-21 23:30:02.845 7604 7604 W boinc : type=1400 audit(0.0:6478): avc: denied { search } for name="2" dev="proc" ino=50415 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.845 7604 7604 W boinc : type=1400 audit(0.0:6479): avc: denied { search } for name="3" dev="proc" ino=50416 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.845 7604 7604 W boinc : type=1400 audit(0.0:6480): avc: denied { search } for name="4" dev="proc" ino=50417 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6481): avc: denied { search } for name="5" dev="proc" ino=50418 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6482): avc: denied { search } for name="6" dev="proc" ino=50419 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6483): avc: denied { search } for name="7" dev="proc" ino=50420 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6484): avc: denied { search } for name="8" dev="proc" ino=50421 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6485): avc: denied { search } for name="9" dev="proc" ino=50422 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6486): avc: denied { search } for name="10" dev="proc" ino=50423 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6487): avc: denied { search } for name="11" dev="proc" ino=50424 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6488): avc: denied { search } for name="12" dev="proc" ino=50425 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6489): avc: denied { search } for name="13" dev="proc" ino=50426 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6490): avc: denied { search } for name="14" dev="proc" ino=50427 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6491): avc: denied { search } for name="15" dev="proc" ino=50428 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6492): avc: denied { search } for name="16" dev="proc" ino=50429 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6493): avc: denied { search } for name="17" dev="proc" ino=50430 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6494): avc: denied { search } for name="18" dev="proc" ino=50431 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6495): avc: denied { search } for name="19" dev="proc" ino=50432 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6496): avc: denied { search } for name="20" dev="proc" ino=50433 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6497): avc: denied { search } for name="21" dev="proc" ino=50434 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6498): avc: denied { search } for name="22" dev="proc" ino=50435 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6499): avc: denied { search } for name="23" dev="proc" ino=50436 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6500): avc: denied { search } for name="24" dev="proc" ino=50437 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6501): avc: denied { search } for name="25" dev="proc" ino=50438 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6502): avc: denied { search } for name="26" dev="proc" ino=50439 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6503): avc: denied { search } for name="27" dev="proc" ino=50440 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:02.849 7604 7604 W boinc : type=1400 audit(0.0:6504): avc: denied { search } for name="28" dev="proc" ino=50441 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.879 7604 7604 W boinc : type=1400 audit(0.0:6808): avc: denied { search } for name="1" dev="proc" ino=50414 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6809): avc: denied { search } for name="2" dev="proc" ino=50415 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6810): avc: denied { search } for name="3" dev="proc" ino=50416 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6811): avc: denied { search } for name="4" dev="proc" ino=50417 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6812): avc: denied { search } for name="5" dev="proc" ino=50418 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6813): avc: denied { search } for name="6" dev="proc" ino=50419 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6814): avc: denied { search } for name="7" dev="proc" ino=50420 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6815): avc: denied { search } for name="8" dev="proc" ino=50421 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6816): avc: denied { search } for name="9" dev="proc" ino=50422 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6817): avc: denied { search } for name="10" dev="proc" ino=50423 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6818): avc: denied { search } for name="11" dev="proc" ino=50424 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6819): avc: denied { search } for name="12" dev="proc" ino=50425 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6820): avc: denied { search } for name="13" dev="proc" ino=50426 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6821): avc: denied { search } for name="14" dev="proc" ino=50427 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6822): avc: denied { search } for name="15" dev="proc" ino=50428 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6823): avc: denied { search } for name="16" dev="proc" ino=50429 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6824): avc: denied { search } for name="17" dev="proc" ino=50430 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6825): avc: denied { search } for name="18" dev="proc" ino=50431 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6826): avc: denied { search } for name="19" dev="proc" ino=50432 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:12.882 7604 7604 W boinc : type=1400 audit(0.0:6827): avc: denied { search } for name="20" dev="proc" ino=50433 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
07-21 23:30:17.629 371 371 W vold : type=1400 audit(0.0:7139): avc: denied { read } for name="fd" dev="proc" ino=56498 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
07-21 23:30:17.629 371 371 W vold : type=1400 audit(0.0:7140): avc: denied { getattr } for path="/proc/340/cwd" dev="proc" ino=56500 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.632 371 371 W vold : type=1400 audit(0.0:7141): avc: denied { getattr } for path="/proc/340/root" dev="proc" ino=56501 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.632 371 371 W vold : type=1400 audit(0.0:7142): avc: denied { getattr } for path="/proc/340/exe" dev="proc" ino=56502 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.665 342 371 E ProcessKiller: Process /data/data/edu.berkeley.boinc/client/boinc (7604) has open file /data/data/edu.berkeley.boinc/client/stdoutdae.txt
07-21 23:30:17.671 342 371 E Cryptfs : unmounting /data failed: Device or resource busy
07-21 23:30:17.705 371 371 W vold : type=1400 audit(0.0:7143): avc: denied { read } for name="fd" dev="proc" ino=56498 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
07-21 23:30:17.705 371 371 W vold : type=1400 audit(0.0:7144): avc: denied { getattr } for path="/proc/340/cwd" dev="proc" ino=56500 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.705 371 371 W vold : type=1400 audit(0.0:7145): avc: denied { getattr } for path="/proc/340/root" dev="proc" ino=56501 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.705 371 371 W vold : type=1400 audit(0.0:7146): avc: denied { getattr } for path="/proc/340/exe" dev="proc" ino=56502 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:17.727 342 371 E ProcessKiller: Process /data/data/edu.berkeley.boinc/client/boinc (7604) has open file /data/data/edu.berkeley.boinc/client/stdoutdae.txt
07-21 23:30:17.727 342 371 W ProcessKiller: Sending Killed to process 7604
07-21 23:30:17.736 342 371 D Cryptfs : Just asked init to shut down class main
07-21 23:30:17.736 342 371 W vold : emulated unmount requires state mounted
07-21 23:30:37.799 371 371 W vold : type=1400 audit(0.0:7147): avc: denied { read } for name="fd" dev="proc" ino=56498 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
07-21 23:30:37.802 371 371 W vold : type=1400 audit(0.0:7148): avc: denied { getattr } for path="/proc/340/cwd" dev="proc" ino=56500 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:37.802 371 371 W vold : type=1400 audit(0.0:7149): avc: denied { getattr } for path="/proc/340/root" dev="proc" ino=56501 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:37.802 371 371 W vold : type=1400 audit(0.0:7150): avc: denied { getattr } for path="/proc/340/exe" dev="proc" ino=56502 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
07-21 23:30:37.836 342 371 E Cryptfs : unmounting /data failed: Device or resource busy
07-21 23:30:37.840 342 371 W SocketClient: write error (Broken pipe)
07-21 23:30:37.840 342 371 W SocketClient: Unable to send msg '200 8 -1'
07-21 23:36:21.690 522 522 I rmt_storage: rmt_storage_connect_cb: clnt_h=0x9 conn_h=0x7f9d77a000
07-21 23:36:21.690 522 522 I rmt_storage: rmt_storage_rw_iovec_cb: /boot/modem_fs2: clnt_h=0x9: req_h=0x9 msg_id=3: R/W request received
07-21 23:36:21.690 522 522 I rmt_storage: wakelock acquired: 1, error no: 42
07-21 23:36:21.691 522 917 I rmt_storage: rmt_storage_client_thread: /boot/modem_fs2: clnt_h=0x9 Unblock worker thread (th_id: 548098016320)
07-21 23:36:21.843 522 917 I rmt_storage: rmt_storage_client_thread: /boot/modem_fs2: clnt_h=0x9: req_h=0x9 msg_id=3: Bytes written = 1572864
07-21 23:36:21.843 522 917 I rmt_storage: rmt_storage_client_thread: /boot/modem_fs2: clnt_h=0x9: req_h=0x9 msg_id=3: Send response: res=0 err=0
07-21 23:36:21.844 522 917 I rmt_storage: rmt_storage_client_thread: /boot/modem_fs2: clnt_h=0x9 About to block rmt_storage client thread (th_id: 548098016320) wakelock released: 1, error no: 0
07-21 23:36:21.844 522 917 I rmt_storage:
07-21 23:36:21.848 522 522 I rmt_storage: rmt_storage_disconnect_cb: clnt_h=0x9 conn_h=0x7f9d77a000Anyway, if anyone else has any other ideas (especially after reading those logs, I'm not at all an expert on these matters so I definitely don't completely know what I'm looking at), I'm all ears.
Thank you all for your time.
Wednesday, 20 July 2016
MM + Root + Xposed + Fingerprint + ENCRYPTION?
Hello Guys and Girls!
I am about to buy a new LG V10 H960a in Germany.
Currently I am using a Galaxy Note 3 which is still a great machine, but I think it is time to switch to a new phone with more speed, better camera and better sound.
I do not game, but listen to a lot of music and take a lot of photos and videos.
At the moment, my phone running stock Android 4.4.4 is rooted, has Xposed and is encrypted.
My question:
After officially unlocking the bootloader on the V10, will I be able to:
Root + install Xposed (Xprivacy, Greenify) + ENCRYPT the device on Stock Marshmallow? (I am not going to install custom roms). Does the method [adb -> pkill -KILL daemonsu] still work? If not, which way do I have to choose?
Also, if I ENCRYPT my device, could you tell me more about the unlocking mechanism?
1. After booting, what is the maximum of letters and numbers possible in the password field [16?]?
2. Is it possible to unlock with the fingerprint sensor after entering a password once after booting?
3. I did not find much info or looked in the wrong place: Generally unlocking with fingerprint, do you have to press once to both wake and unlock or do I have to press twice for wake and once again for unlock?
Thank you very much!
A new member to this community.
I am about to buy a new LG V10 H960a in Germany.
Currently I am using a Galaxy Note 3 which is still a great machine, but I think it is time to switch to a new phone with more speed, better camera and better sound.
I do not game, but listen to a lot of music and take a lot of photos and videos.
At the moment, my phone running stock Android 4.4.4 is rooted, has Xposed and is encrypted.
My question:
After officially unlocking the bootloader on the V10, will I be able to:
Root + install Xposed (Xprivacy, Greenify) + ENCRYPT the device on Stock Marshmallow? (I am not going to install custom roms). Does the method [adb -> pkill -KILL daemonsu] still work? If not, which way do I have to choose?
Also, if I ENCRYPT my device, could you tell me more about the unlocking mechanism?
1. After booting, what is the maximum of letters and numbers possible in the password field [16?]?
2. Is it possible to unlock with the fingerprint sensor after entering a password once after booting?
3. I did not find much info or looked in the wrong place: Generally unlocking with fingerprint, do you have to press once to both wake and unlock or do I have to press twice for wake and once again for unlock?
Thank you very much!
A new member to this community.
SD card encryption
Hi
I am setting up my new phone, I have purchased a new SD card but before I set it up would like to know is it advisable to set it up at encrypted or just normal,
I would like the extra encryption but the problem of it not being accessible anywhere is a problem
What if my phone was to stop working or just die all of a sudden, it's not a big brand so could happen....will I lose all the data if that was to happen?
Can I buy another phone same model and use the card in there ?
Any recoveries out there that allow access to the encrypted SD card
I would just like a little clarification as it seems confusing
Thanks
Sent from my m8 using Tapatalk
I am setting up my new phone, I have purchased a new SD card but before I set it up would like to know is it advisable to set it up at encrypted or just normal,
I would like the extra encryption but the problem of it not being accessible anywhere is a problem
What if my phone was to stop working or just die all of a sudden, it's not a big brand so could happen....will I lose all the data if that was to happen?
Can I buy another phone same model and use the card in there ?
Any recoveries out there that allow access to the encrypted SD card
I would just like a little clarification as it seems confusing
Thanks
Sent from my m8 using Tapatalk
Tuesday, 19 July 2016
TWRP won't remove encryption
Hello everyone,
I am running 3.0.2-2 on the SM-G935FD and for whatever reason TWRP won't wipe the encryption, thus I cant read the internal SD card. I am getting the " /data mount" error.
I have done the advanced wipe and cleared everything except the external SD, am I using the wrong TWRP? any ideas?
I am running 3.0.2-2 on the SM-G935FD and for whatever reason TWRP won't wipe the encryption, thus I cant read the internal SD card. I am getting the " /data mount" error.
I have done the advanced wipe and cleared everything except the external SD, am I using the wrong TWRP? any ideas?
Monday, 18 July 2016
How to enable facebook messenger encryption on Android
Hi all,
How is this done?
Kind Regards
TwinAdk
How is this done?
Kind Regards
TwinAdk
Saturday, 16 July 2016
Huawei Y5 2 Encryption
Hello. I renctly bought a Huawei Y5 2 with Android 5.1, I want to encrypt my phone but as I can see in the settings/security menu I cannot choose that option, and I just read that Huawei does not let you encrypt it. So i was wondering, is there any way to use a 3rd party app or something like that to encrypt my phone? Full disk encryption is a must.
Thanks
Thanks
Wednesday, 13 July 2016
G4 Stuck in Encryption mode.
Hi I bought a refurbished LG G4 and I set it up and used it for one day and it was great. But I went into the about section and noticed that it wasn't running Android 6.0 yet so I connected it to LG bridge and updated it through the program. Next thing I know after it finished updating it booted into encryption mode asking for a password. I try enter something and it goes to 29 attempts out of 30 if I try it again it just stays there and doesn't change or or go below 29 it has now randomly changed into Chinese too.
I contacted the company I bought it off and explained it to them and said there should have been an explanation in my package. But there wasn't.
It's not allowing me to boot into recovery and I have no idea what to do.
I used this phone for one day and spent a lot of money on this phone and I have no idea what I can do to fix this situation.
I contacted the company I bought it off and explained it to them and said there should have been an explanation in my package. But there wasn't.
It's not allowing me to boot into recovery and I have no idea what to do.
I used this phone for one day and spent a lot of money on this phone and I have no idea what I can do to fix this situation.
Sunday, 3 July 2016
CyanogenMod 13 disk encryption and TWRP
I'm running TWRP 3.0.2 with nightly CyanogenMod 13. I'd like to know what's the progress on fixing the bug where you can't mount the encrypted storage even if your typed PIN is correct.
I know there are a few workarounds as to updating CM (like copying the zip file to cache and flashing it), but I'd like to know if there's any progress to fix this bug.
I know there are a few workarounds as to updating CM (like copying the zip file to cache and flashing it), but I'd like to know if there's any progress to fix this bug.
[Q] Encryption unsuccessful on LG G3 D855 Stock Android 6 Marshmallow
Hi!
I got some major problems with my G3. I was on stock Android 6 (rooted). Worked fine for some months. Then I decided to encrypt the phone and activated this option in the normal android settings. After some time the phone restarted and I got the "Encryption unsucccessful" page and cannot do anything anymore.
After reading through the help forums I tried the following steps to solve it:
- factory reset
- wipe eveything in twrp and flashed system, boot, modem manually to Android 6 again
- repaired all filesystem partitions in twrp
- many many more factory resets
All didn't help. The only thing that changed is that when coming to the "Encryption unsucccessful" page now the phone hangs up after the next option I choose (shut down or restart or factory reset) so I have to take out the battery to restart or shut down.
Any suggestions how to solve it and maybe also any suggestions what might have gone wrong? Don't want to kill the next phone the same way by just enabling encryption!?
I got some major problems with my G3. I was on stock Android 6 (rooted). Worked fine for some months. Then I decided to encrypt the phone and activated this option in the normal android settings. After some time the phone restarted and I got the "Encryption unsucccessful" page and cannot do anything anymore.
After reading through the help forums I tried the following steps to solve it:
- factory reset
- wipe eveything in twrp and flashed system, boot, modem manually to Android 6 again
- repaired all filesystem partitions in twrp
- many many more factory resets
All didn't help. The only thing that changed is that when coming to the "Encryption unsucccessful" page now the phone hangs up after the next option I choose (shut down or restart or factory reset) so I have to take out the battery to restart or shut down.
Any suggestions how to solve it and maybe also any suggestions what might have gone wrong? Don't want to kill the next phone the same way by just enabling encryption!?
Labels:
Android,
D855,
encryption,
Marshmallow,
Mobile,
Stock,
unsuccessful
Saturday, 2 July 2016
Disable OxygenOS storage encryption?
Is it possible to disable storage encryption without wiping data?
Qualcomm encryption flaw
Hi everyone
Just thought it's good to know these news as this is a serious flaw for those of us that are using encryption in their phones.
http://www.zdnet.com/article/how-to-...tag=RSSbaffb68
What this means is probably that encryption on our Qualcomm based phone will not be fixable, really serious problem I would say. :-/
Just thought it's good to know these news as this is a serious flaw for those of us that are using encryption in their phones.
http://www.zdnet.com/article/how-to-...tag=RSSbaffb68
What this means is probably that encryption on our Qualcomm based phone will not be fixable, really serious problem I would say. :-/
Subscribe to:
Posts (Atom)