Develop Bugs

Be warned: Encrypting your device can be dangerous

Hello,
As Google has decided to turn encryption on as a standard in the upcoming Android 5.0, I thought I would give it a test on my CosmicCM 5.4.
I started the encryption and it prompts you that you for a passcode that will be used from now on, so far no problem.
It started encrypting my device and it was running for some time(I left it alone for an hour) and reboots a couple of times.
After he's finished the annoyance came.
first you will have to type twice your password with a reboot, one time do decrypt your device the second time to enter your device.
Be aware that performance can be slowed through encryption, and it can negatively impact battery life too.
So I decide to go back.
The Problem: Once encrypted, you can't decrypt it easily.
When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset and this works.
Now I wanted to try a rom (TW 4.2.2 based) and see how this worked and after installing and booting.
I got prompted to enter the decryption and of course this didn’t work anymore as there is no data for the password.
So I assumed you can wipe everything from your custom recovery mod (CWM, TWRP, or one of those).
Wrong! You'll get beautiful "can't mount /data" messages and more.
After some hard time I got everything working again, by flashing CosmicCM again.
The phone booted al clean again without asking for encryption and when you check the menu it also mentioned encryption is deactivated.
Trying the previous rom again just triggerd the encryption again.
So It seems that there is still somewhere a hidden encrypted protection that will be activated when I flash a different rom.
So be warned and don’t play with encrypting your device as you could brick it.
Didn't have time to investigate further on how I can remove it completely, but my guess is I have to redo all the partitions.

I was on the same boat a month ago

akiratoriyama said:
I was on the same boat a month ago
Click to expand...
Click to collapse
I wish you told me sooner
Did you redo all the partitions to get the encryption completely removed?

RichyE said:
I wish you told me sooner
Did you redo all the partitions to get the encryption completely removed?
Click to expand...
Click to collapse
I think I had to wipe my data via Philz, CWM and stock to remove encryption.

akiratoriyama said:
I think I had to wipe my data via Philz, CWM and stock to remove encryption.
Click to expand...
Click to collapse
Thanks for the info, will try to flash stock this week and see if this helps

Stuck at lockscreen (pattern not recognised)

Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?

PriyanPhoenix said:
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
Click to expand...
Click to collapse
In this case, even a factory reset might not help.

Just to confirm, should anyone else have the same issue, a factory reset did solve the problem and the error has not returned. Still no idea what could have caused it though.

Solution
I had this problem also just hold the power button down for like a minute.

I'm having the same problem, was working fine a few hours ago then not recognizing the pattern. I've tried holding the power button but that just powers it off. When I turn it back on it asks for my pattern to power the device back on and it recognizes the pattern then just fine but once it power's up and I try to put the same pattern in to unlock the screen it says wrong pattern!! What the hell is going on here? Any help please?

This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.

NJ72 said:
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
Click to expand...
Click to collapse
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.

1barlog17 said:
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
Click to expand...
Click to collapse
Yes, Google sent me a new unit. They didn't advise to do a factory reset, they just advised to return the unit. Part of their RMA process is that they recommend you wipe data (for data protection) so I ended up doing both.
I imagine that there are other apps which would offer access to your device data without unlocking, I just have experience with Airdroid.

I also had this problem, but I was using a pin instead of a pattern. Very concerning to be locked out of your own tablet. Had the tablet for about 3 months before it happened. Factory reset fixed it, hasn't returned since but only time will tell. Doesn't inspire a lot of confidence in the device knowing that maybe you could get locked out at any moment.

The same problem has been found on the Nexus 6p. Lockscreen not unlocking with the correct pin/password, appears to be a problem with the lockscreen as the phone can be booted or decrypted with the correct password.
The suggested fix was to ensure you have prey or another similar program installed. Changing your unlock password remotly via prey fixes the problem allowing you access to your phone.

Just had this problem today. Went to login with the same pattern I've been using for the past 3+ months, and it said "Wrong Pattern" over & over again. I tried to reboot and try again, same story. I used Android Device Manager to lock it & entered a password. Then my Pixel C confirmed that it was locked via the Android Device Manager, but when I went to log in, it asked me for a pattern, not a password! (Bad sign!) And, of course, I entered the right pattern and it told me it was the wrong pattern.
The Google support rep said I had to do a factory data reset. It is indeed disconcerting and frustrating. Next time I'll use Backup!

are you guys rooted? I had this problem on my N5X during rooting and trying to install ROMs. wiping data helped but I simply reset the device anyway. I noticed this also happened on some devices when an incompatible version of SuperSU was installed. If not rooted then you got me.

I am not rooted. I haven't done anything to the tablet except install & use apps and install a p12 certificate (which, I believe, unfortunately, requires you to use some kind of lock screen).
So, I used Android Device Manager to erase my tablet & the problem went away. Yay! I changed to using a PIN instead of a pattern. Now, today, just over a week later, the problem has recurred. <sob!> It says "Wrong PIN" when I try to login, even after powering off & on again, and I am facing the prospect of having to go through all that again.

Just had the same issue, tablet not rooted no developer options unlocked/used just left as factory with apps installed from play store.
Factory reset in progress...

Just happened to me (on the official beta ROM)

This just happened to me today on my Pixel C. I found threads on Google Forums that this has been happening for over a year without a fix.

If your bootloader is unlocked, you can always boot TWRP, Advanced > File Explorer, change to /data/system and delete locksettings.db, locksettings.db-wal and locksettings.db-shm.

Does anybody has an idea here? I'm confronted with this issue: Wrong PIN. No matter how many times i give the correct PIN
restarting Pixel C does not help. Is there any other way to fix this issue?
Shame on Google for this!

farsiray said:
Shame on Google for this!
Click to expand...
Click to collapse
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.

bornheim2 said:
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
Click to expand...
Click to collapse
Looks you have no clue what you're talking about. Do some more reading before you give a useless comment.
This is an issue with Pixel C since 2016, Google still hasn't fixed it.
https://issuetracker.google.com/issues/62404336
https://productforums.google.com/fo...ce=footer#!msg/nexus/ImQsmQ8-8JA/n-1kqOv9AwAJ

Set up 5x as new Device or from Previous backup? (to best improve poor performance)

Hello,
My 5x became more less unusable so I had to factory reset it. Will setting it up as new device be more advantageous in terms of performance? Or should I stick with the backup and save my self a lot of time downloading everything?
I had this phone since it came out and I think I will be getting rid of it. It became laggy as hell and 2gb of ram just does not cut it, and now since I just upgraded from 6.0 to 6.0.1 my build number is MTC19V and for the life of me I cant find a way to decrypt it. Encrypted 5x is even worse (I've done both so had a feel for it with and without it)

neopl666 said:
Hello,
My 5x became more less unusable so I had to factory reset it. Will setting it up as new device be more advantageous in terms of performance? Or should I stick with the backup and save my self a lot of time downloading everything?
I had this phone since it came out and I think I will be getting rid of it. It became laggy as hell and 2gb of ram just does not cut it, and now since I just upgraded from 6.0 to 6.0.1 my build number is MTC19V and for the life of me I cant find a way to decrypt it. Encrypted 5x is even worse (I've done both so had a feel for it with and without it)
Click to expand...
Click to collapse
Check out this thread
https://www.reddit.com/r/nexus5x/comments/4nayhm/to_those_of_you_with_lag_force_closes_etc/
factory reset and set up as new google account to experiment and see if there is still lag. Just load up a couple of your most used apps to start.
I've run encrypted and unencrypted side by side on 2 5xs on same build with same exact software loaded and there was no noticeable difference within Android. I doubt your lag is because of encryption.
Also if you are running out of memory it just takes a little longer to switch to an app, it doesn't lag all the time. If it is lagging all the time, that is caused by something else.
Any chance you were running low on storage space? 2GB or less free? If so, there's a decent chance that was causing lag as EMMC drives don't perform well when they start getting full.
The way you run decrypted on MTC19V is the same as on previous releases. It hasn't changed.
Use TWRP to install SuperSU then boot into bootloader
fastboot erase user
fastboot format user
If you need root, boot into TWRP and reinstall SuperSU as last two steps will overwrite SuperSU.

sfhub said:
Check out this thread
https://www.reddit.com/r/nexus5x/comments/4nayhm/to_those_of_you_with_lag_force_closes_etc/
factory reset and set up as new google account to experiment and see if there is still lag. Just load up a couple of your most used apps to start.
I've run encrypted and unencrypted side by side on 2 5xs on same build with same exact software loaded and there was no noticeable difference within Android. I doubt your lag is because of encryption.
Also if you are running out of memory it just takes a little longer to switch to an app, it doesn't lag all the time. If it is lagging all the time, that is caused by something else.
Any chance you were running low on storage space? 2GB or less free? If so, there's a decent chance that was causing lag as EMMC drives don't perform well when they start getting full.
The way you run decrypted on MTC19V is the same as on previous releases. It hasn't changed.
Use TWRP to install SuperSU then boot into bootloader
fastboot erase user
fastboot format user
If you need root, boot into TWRP and reinstall SuperSU as last two steps will overwrite SuperSU.
Click to expand...
Click to collapse
Thank you for your post. I think the issue with my phone is that overtime it just became increasingly slower. I always kept at least 6gb of free space as I am aware of the issue of not doing so. Taking off encryption soon after I purchased the phone when it came out did make it more responsive. I now wiped it and loaded 6.0.1 and can say that the phone came back to life. But for how long? This time around I will try to not tweak the hell out of it and to not load too many things through xposed as those were probably the culprits of poor performance over the months.
I will try the commands you recommend to remove encryption, what I did before that failed to work was format the data partition through TWRP. Will my phone remain unencrypted if I side load the next OTA, or will side loading the OTA encrypt it back up? Thanks again!
PS. I am considering OnePlus 3 but the (incredibly timely) review on Anandtech states that the color calibration of the screen is some of the worse out there, and that may just be the deal breaker. It is a shame really as otherwise it is looking like a one fine device.

neopl666 said:
Thank you for your post. I think the issue with my phone is that overtime it just became increasingly slower. I always kept at least 6gb of free space as I am aware of the issue of not doing so. Taking off encryption soon after I purchased the phone when it came out did make it more responsive. I now wiped it and loaded 6.0.1 and can say that the phone came back to life. But for how long?
Click to expand...
Click to collapse
I tested starting with April release. It is possible with earlier releases encryption was slower, but with April release side-by-side comparison with encrypted vs unencrypted there was no noticeable difference. I loaded reasonably large games, offline GPS maps, web browsing, etc.
Sometimes it is hard to tell if unencrypting is the reason the phone is faster, because as part of unencrypting, you essentially do a factory reset when your user partition gets wiped/reformatted. It is possible your phone could have been faster just by the factory reset with no decryption.
neopl666 said:
I will try the commands you recommend to remove encryption, what I did before that failed to work was format the data partition through TWRP. Will my phone remain unencrypted if I side load the next OTA, or will side loading the OTA encrypt it back up? Thanks again!
Click to expand...
Click to collapse
The critical step is *never* boot using a factory boot.img. Then you can remain decrypted.
If you sideload an OTA, immediately boot into bootloader when done, then to recovery. I say boot into bootloader, because sometimes you can mistime the boot into recovery, and boot into android by mistake. I don't remember if sideload immediately reboots when done or gives you some time, but you need to get into bootloader (or TWRP recovery, either directly or via bootloader menu option) prior to initial boot with the stock boot.img, otherwise it will reencrypt.
From TWRP you'll need to flash the SuperSU install zip and that will patch your boot.img to remove foreced encryption. From that point on you are safe.
Honestly, I ran for a month decrypted even though I found no difference in performance between encrypted and unencrypted, just in case there were long term differences. It wasn't until I found a separate issue with my SIM card and visual voicemail that only occurred on decrypted sytems that I switch back.
It's been a few weeks and there have been no noticeable slowdowns for my usage, but I don't have 2 units to run side-by-side right now, so I can't say with as much surety as I could when I literally ran them side-by-side and pressed on the same apps and did the same actions.

Possibilty of Data/Storage Recovery?

Hey there,
let me start off by saying that I don't own an XL, but a non-XL 3a. Since my question seems to apply to both devices (similar/same components), I'll try my luck here.
Recently, my 3a got stuck in SystemUI crashes and I tried every solution that came to mind and others suggested over at the 3a section (check my profile if curious, basically locked BL, fully stock, no ADB), but nothing solved the issue.
However, I didn't factory reset yet, but I'm confident that it would fix it. On the other hand, It'll also wipe my storage.
----
Long story short, the only option I can think of is to recover my files with a data recovery app/program after I have wiped/factory reset my phone.
Did anybody ever successfully used such an app on a Pixel or similar (A/B) partition layout? Is it even possible/viable? Are there special prerequisites to consider?
It goes without saying I'll make sure to overwrite as few sectors as possible, if any. I can accept some files getting lost in the process, but want to keep whatever I can recover.
Thank you for reading.

Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.

Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.

xnifex said:
Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.
Click to expand...
Click to collapse
acejavelin said:
Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.
Click to expand...
Click to collapse
Well, damn. Thanks nonetheless, I didn't even think about that.
I'll try to fiddle with the phone one last time, maybe I'll get it unlocked somehow (I can only get 7 or 8 dots
of my pattern connected before the UI crash kicks in...). This is literally the only thing that separates me from the storage.
This has to be the most infuriating small obstacle with the biggest effect for me.

Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/

brandontowey said:
Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/
Click to expand...
Click to collapse
Man, if that works out, I'd be insanely glad. Have to get my hands on my friend's laptop first though.
I mean, the UI just started crashing after I checked for an OTA without downloading, then changing the wallpaper. That was literally it. Hadn't I rebooted, I would have been able to still unlock with my fingerprint between each crash.
Here's hoping that ADB sideloading OTAs left that slot option intact.
Will definitely update this post; at the very least, thank you for your suggestion.
Update: "fastboot continue" as well as switching boot slot parameters aren't allowed on this locked bootloader.
ADB sideloading caused slots to switch anyway, and both slots seemed to be affected from the SystemUI crashing. Will edit my original thread with a conclusion now.

Question February Update caused my phone to reboot all the time

Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?

How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com

fil3s said:
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Directly through the phone's regular system update.

WHOneedsSOX said:
Directly through the phone's regular system update.
Click to expand...
Click to collapse
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?

fil3s said:
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
Click to expand...
Click to collapse
That's correct, it isn't unlocked.
RetroTech07 said:
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
Click to expand...
Click to collapse
I have done absolutely no modifications other than typical downloading of apps and modifying through there but even that is just theming. By "try again," just wipe and then reinstall the update?

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).

As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.

Morgrain said:
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
Click to expand...
Click to collapse
I'd be happy with 2 random reboots per day. Not even kidding, I must be at 100 a day. It's super random too. None from 9 am until around 1pm and then all of a sudden 10 in a row.
I'm pretty sure it's a software issue, had no random reboots before I installed the February update. Will probably try reformatting the entire phone first and see how that goes.
DanielF50 said:
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Click to expand...
Click to collapse
Thanks, will try this out if a reformat doesn't work.

Try safe mode and see if it still happens.

neyes said:
Try safe mode and see if it still happens.
Click to expand...
Click to collapse
Still happened in safe mode.

I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.

RetroTech07 said:
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
Click to expand...
Click to collapse
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?

WHOneedsSOX said:
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
Click to expand...
Click to collapse
Official Google Android Flash Tool

roirraW edor ehT said:
Official Google Android Flash Tool
Click to expand...
Click to collapse
Thanks!