Hey Guys,
I just flashed the latest lineageOS nightly and decided it was a good time to encrypt my phone.
However, when I try and encrypt, it starts by going to the encrypt screen with the green outline of the android guy. Seconds later it goes to the lineage loading animation and goes right back into the OS and nothing happened (no errors or anything either) I've tried multiple times (unplugging and plugging the phone back in, turning off wifi, etc)
Has anyone else come across this?
Thanks!
Has no one tried encrypting their phone? I can't be the only one.
I tried to encrypt using lineage 13 for the zl1 (lepro3) March 25th weekly build, and see exactly this issue.
Can't remove data
I've tried encrypting my phone several times and never had this issue. My problem comes when app data for certain games are still saved on my phone, even if I do a factory reset right after encrypting. The specific apps I'm referring to are Mobile Strike and Game of War.
Related
I'm running CM 10 on my EVO. I haven't updated it in a while so it's probably 10.1 or something. Random shutdowns would happen for no reasons sometimes when using the new YouTube app. Then yesterday when I turned on Bluetooth, the phone shutdown by itself. When it reboots it says Android is upgrading... and optimizing apps. Then it reboots and gets stuck in a bootloop. I can boot to bootloader and recovery. I've wiped cache, Dalvik cache, and nothing seems to fix it. Sometimes it boots and I can enter my PIN and use the phone for a few seconds until it reboots itself again. Also, there has been discolored streaks near the sides of the screen. When using the phone they're black, but when the screen is booting they're red on top of the black.
Does anyone have experience with such a problem? I want to try fixing this so I can backup my data before I reflash the ROM or anything.
If it's an older CM release that could be part of your problem. I would update to CM 10.2 and see if the problem persists. I'm currently running the 8/24 IRC build and it has been rock solid. If you continue to have issues you may have a hardware problem.
Sent from my EVO using XDA Premium 4 mobile app
Thanks for the reply. I did a wipe/factory reset from recovery after doing a backup. Everything seems to be okay now. I'm flashing CM 10.2 8/30 from the IRC to try it out.
I have a backup of the state when it wasn't booting properly. I was wondering if anyone had a similar problem with the turning on Bluetooth and then the shutting down by itself and bootloop. I want to be able to recover files from that state.
Sup guys, so i just had a really strange problem that popped out randomly, i was watching a youtube video and i had to help a person quickly and when i came back just a minute later i saw my phone showing encryption unsuccessfull when i pressed the power button to turn my screen on. Well it said to factory reset my phone, i don't store any important data on my phone anyways so i just went for it, and it restarted went to my TWRP recovery and tried factory reseting it, to no success. It basically failed to access /data/ and other directories and i can't see any files in them through recovery. And so i can't even factory reset it, i can't install a ROM cause the partition is corrupt i assume. How can i "unbrick" this? I was running the good old Temaseks CM 12.1 ROM, has been working fine for a looong time. My PC recognizes the phone but i can't access any data, it just shows that it's connected, odin doesn't recognize it.
Can somebody help me please ? I use my phone alot and it's really important.
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
I haven't tried full device encryption before, so I thought I'd give it a try with my old i9100. It was running twrp-3.1, Lineage 14.1 (specifically the OctOS flavour) and had OpenGapps and Lineage Root installed. I proceeded to set up a pin, enable full device encryption, it rebooted and I began to wait. Several hours later it was still spinning with the boot animation. One post online suggested a rooted phone could give it issues. No worries, there was nothing of value on there anyway. Rebooted back to twrp, reinstalled the OS, OpenGapps, factory reset, let it reboot and I was back to the launcher. Set a pin, tried to click on the "Encrypt Phone" entry in settings and nothing happens. The encrypt phone window just won't come up. From there I proceeded to try several things. Various combinations of pins and passwords in different lengths. Reinstalled the OS a few more times with and without OpenGapps. Downgraded to Lineage 13. Nothing. Never again have I got the encrypt phone window to come up.
Is there some sort of prereq that I'm missing that I haphazardly had on my first install that I haven't repeated?
Thanks
Same problem here, well, not really, mine reboot and nothing happens except that i don't have network anymore, i have to reboot the phone again to have network operational.
But the phone isn't encrypted, tried everything without success.
I can see post on forum from the beginning of the year with this issue, too bad for us, encryption is a really important feature for a lot of users.