Database Develop

Friend got the update and now is having none stop issues.

I am filling in the info for him but he told me today that as of the update he gets freezing, only half the apps and info loads, can't see any of his text and he has done about 5 battery pulls already. Prior to the update everything was smooth sailing, he is not rooted and when he got the update he left the phone alone to do it's thing the entire time.

mentalcase87 said:
I am filling in the info for him but he told me today that as of the update he gets freezing, only half the apps and info loads, can't see any of his text and he has done about 5 battery pulls already. Prior to the update everything was smooth sailing, he is not rooted and when he got the update he left the phone alone to do it's thing the entire time.
Click to expand...
Click to collapse
Tell him to wipe his data, that should help clear out anything strange.

danifunker said:
Tell him to wipe his data, that should help clear out anything strange.
Click to expand...
Click to collapse
I already told him he will probably have to lose everything but I was hoping to maybe give him another alternative.

mentalcase87 said:
I already told him he will probably have to lose everything but I was hoping to maybe give him another alternative.
Click to expand...
Click to collapse
I agree with danifunker. Just back his user data (pics, music, etc.) up to external-sd if it isn't already there. You can try backing his user apps up with Titanium Backup, but YMMV with that. You're reintroducing variables back into the flash.
I have also seen quite a few cases where selecting the backup/restore phone with Google during the initial setup after a major OS update has caused issues as well. This happened on quite a few employee phones here where I work during a previous upgrade. So much that it's our standard policy to not select them after a major upgrade. If a data wipe doesn't solve it, a full system restore and unselecting those options during setup is another (destructive) alternative.
Good luck amigo. Keep us posted. :highfive:

Brand new Nexus 6 stuck in optimizing apps loop

Hey all, I recently got my nexus 6, and out of the box it worked fine. I started trying it out, and realized things were crashing quite often, like google play, and gmail. Then it prompted me to install the Android 5.1 update, which is when all this started.
Upon finishing the upgrade my nexus 6 cannot get past the Optimizing Apps screen, as soon as it gets onto the "Starting Apps" state, it will simply crash, and start over, booting again. This has been very frustrating since I just got this device and want to enjoy it. I have not rooted it, I have not tampered with it and the bootloader is locked. I tried cleaning the cache partition but that didn't help. So is anyone else experiencing this with their nexus 6? I really need a way to fix this, and if I have to flash the stock image onto it, then I will. But since the bootloader is locked is that even possible?
Please help me, I don't want to send it back in and wait another eternity.

Yes it's possible. However. Try a factory reset from recovery first.

graydiggy said:
Yes it's possible. However. Try a factory reset from recovery first.
Click to expand...
Click to collapse
I've done that a zillion times. It's not working, my phone refuses to get past the "Android starting..." screen. So if you could walk me through how to flash, since I couldn't find a guide online.

I called google support, and they want to replace it. So I'm gonna do exactly that.

I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.

[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
third? that makes it seem as you are the one thats not doing something right. just saying. one, ok, it happens. two, chances are very slim, but it can happen, mist likely wont. three, you are doung something wrong. if you factory reset, then it boots without android is upgrading. when you add apps, change apps, or change things in your system, or wipe dalvik, then android is upgrading happens.

[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
DEFINATELY operator error...
they don't "all do this", otherwise the THOUSANDS of us here on XDA who flash things constantly without issue every day would be experiencing the same thing..

72 Hour Lockout When Flashing Rom's

I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.

Remove your google account before the factory reset??

holeindalip said:
Remove your google account before the factory reset??
Click to expand...
Click to collapse
Will that help?

Won't ask for the previous google account on login from factory reset

holeindalip said:
Won't ask for the previous google account on login from factory reset
Click to expand...
Click to collapse
Really? I'm going to have to try this. Would save a huge headache; I'll report back.

stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
I searched a bit and found this:
http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
If that article is correct, the "chance" isn't something random, it is caused by changing your google account password. So to avoid, don't factory reset within 72 hours after changing your google account password.

http://forum.xda-developers.com/showthread.php?t=3104504

As long as you do a full device wipe before flashing you are fine. I have never had this pop up. Just properly format system, data and both caches then flash. Simple and the only real way to flash a rom.

Tried to disconnect the account, doesn't work.

Matter of fact I did change my google password recently, maybe that's why I can't do ****.

stevew84 said:
Matter of fact I did change my google password recently, maybe that's why I can't do ****.
Click to expand...
Click to collapse
That would be it.

zelendel said:
That would be it.
Click to expand...
Click to collapse
I did that on the 10th, so one more day.

stevew84 said:
I did that on the 10th, so one more day.
Click to expand...
Click to collapse
Nothing to do but wait and see. Mind the swearing. The stars dont prevent infractions. Friendly warning.

stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
Leave 'OEM unlocking' enabled in developer options. It disables this feature.

It resets every reboot

holeindalip said:
It resets every reboot
Click to expand...
Click to collapse
No, it's a sticky setting that is saved somewhere else. It even survives formatting of the system partition.

On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0

holeindalip said:
On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0
Click to expand...
Click to collapse
i never knew it other as being sticky. Anyway... leaving it enabled disables the "forced" login to the original Google account. I was locked out once before. When that happened i restored a working TWRP backup. Rebooted and enabled 'OEM unlocking' and never had a forced login again (i flash about 2 or 3 times a day). Also... check the popup when you enable "OEM unlocking".

Yeah all device security goes out the window with it left on

I got bitten by this problem. Until there is a solution I just have to wait the 72+ hours?

G890A freezing during installs/updates and bootup after - narrowing the problem

Currently have a G890A, AT&T, Android 6.0.1, Baseband: G890AUCS5CPK4
I've spent days of time trying to understand and fix repeated freezes/crashes, and am curious if you think my understanding of the problem is likely accurate and if the next steps make sense. Below are current issues, my previous solution attempts, best guess at the problem, and next steps to solve it. Thanks for taking the time to read this!
Issues:
- Starting at the Android 6.0 update, the phone began freezing intermittently when installing/updating certain apps.
- Freezing was unaffected by subsequent firmware updates
- Freezes happened before I could see which apps were starting to auto-update.
- During a freeze, the phone gets warm and drains the battery quickly. Power+down will reboot the phone, then it usually freezes again.
- After the first freeze, freezes and crashes would then continue on bootup, sometimes over 20+ reboots, usually while drawing "SAMSUNG" letters or soon thereafter
- Eventually whatever was installing/updating/uninstalling seems to take, and the phone finally stops rebooting.
- Disabling auto-updates prevents freezing
- After a factory reset it takes hours of rebooting, getting lucky enough to see the home screen, and for luck to hold long enough to open the play store before a freeze happens
- Freezing does not happen when updating every app. Installing/updating Google Inbox and Khan Academy both caused 20+ reboots/hangs. Trying to uninstall Khan Academy produced another 20+ until the uninstall finally seemed to take. I haven't tried to uninstall or update Inbox.
Current efforts to fix the problem:
- Safe mode: no improvement
- 3 factory resets: no improvement
- 3 factory resets + safe mode: no improvement
- Disabling auto-updates: effective, as long as I never install or update apps
- calling ATT: They said go to a Samsung rep at Best Buy
- talking with Best Buy Samsung rep (closest is an hour drive away): Best Buy says they can re-flash G890AUCS5CPK4, but my concern is that whatever got corrupted in an earlier update won't be fixed by re-flashing that version.
- calling Samsung: Samsung says they'd be happy to look at it if I send it to them a couple weeks. They also state that they'll send it back untouched if I try flashing it myself.
Best Guess About the Problem
Something got corrupted in Play Services during the 6.0 update; something that runs early in bootup and continues any in-progress installation/update processes.
Next Steps
- Determine on this thread whether it makes sense to reflash G890AUCS5CPK4 at Best Buy
- If so, take the phone to Best Buy for a reflash. If not, find a backup phone for a couple weeks and send the GS6 to Samsung
- Prefer not to try flashing it myself since I have no experience and don't want to brick it or remove the chance for Samsung to fix it as a backup plan.
Do the best guess and next steps make sense? I really like the s6 active. I've had it just over a year and want to keep it for a while. It's gone rafting, kayaking and hiking in all kinds of weather, and operated flawlessly in and out of water the entire time. Fantastic phone until this issue.
Thanks again!
Adam

How are you installing your apps? One by one from the play store, all at the same time from the play store, or by some other method (from an archive of some kind), which might be corrupt.

anneoneamouse said:
How are you installing your apps? One by one from the play store, all at the same time from the play store, or by some other method (from an archive of some kind), which might be corrupt.
Click to expand...
Click to collapse
@anneoneamouse, Great question. Thanks for asking. I did a few of them via Samsung's Smart Switch, then uninstalled most of those. I didn't think about the APK's stored by Smart Switch being corrupted somehow. Trying reinstalls from the Play Store now.
And... it's been about 3 hours. A number of previously failing apps worked when installed from the Play Store. I was excited. Then I uninstalled Google Inbox and reinstalled it from the Play store, and the phone froze. Multiple reboots never got it past the loading screen after that. Eventually I did a factory reset. The phone still froze with only factory apps. No non-factory apps installed from any source. Four more factory resets later, no progress. It's probably time to send this critter to Samsung.

Have you tried booting into the recovery menu, and clearing all the cache areas? I'm not sure that a factory reset is equivalent to a complete wipe.
How are you uninstalling Google inbox?

anneoneamouse said:
Have you tried booting into the recovery menu, and clearing all the cache areas? I'm not sure that a factory reset is equivalent to a complete wipe.
How are you uninstalling Google inbox?
Click to expand...
Click to collapse
Sorry for the slow reply. Just saw this. I did cache wipes followed by resets, which also log to the screen that they're doing a cache wipe. Uninstalling/reinstalling inbox stopped being an issue because I could never get far enough to install Inbox again from any source. As soon as I logged in with a google account during setup, the factory apps started updating and the hanging/crashing began. Sent it to Samsung.
Appreciate your help!

STOP - Read before doing OTA of Android Pie

I tried an OTA of Android Pie tonight, this was from EE UK.
First the system update couldn't verify, so I had to hard power off the phone, on powering on it re-installed and loaded up.
I unlocked the phone from the lock screen and it went to "Android Starting" and after a few moments rebooted.
Now the phone loads up but I can't unlock it, I just get constant PIN incorrects. It's a software issue because you never get to the limit of pin attempts, or the forgotten password option.
Contacted Sony, they've heard of it numerous times today, can't do anything about it.
They'll tell you to use Sony Companion to backup and restore, which you can't do unless the phones unlocked. So basically demand a full reset all data lost.
Update at your own risk, maybe consider removing device pin before the update if you can.

Same problem here in France.
There's a thread on talk.sonymobile: https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Can-t-access-phone-after-updating/td-p/1351581/page/2
So far no working solution.
The french sonyxperia twitter account is also useless.

No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...

zwan33 said:
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
Click to expand...
Click to collapse
backup ur photos/videos and make a factory reset, everything works flawlessly for me.

rideti.me said:
So basically demand a full reset all data lost.
Click to expand...
Click to collapse
It's a painful lesson, but backing up everything before doing anything is a must, even when doing something like an OTA update which you expect to work. I'm just waiting for a customized UK ftf to become available and will be doing a complete wipe which alleviates any unforeseen conflicts.

I had full backup, the corruption was in the pincode, therefore encryption control is lost. The backups are encrypted, I've recovered apps, messages, contacts etc.... But none of the appdata was recoverable without de-crypt.

I feel lucky: I used the repair function because I did not want to have all those small issues usually coming with a big OTA update. I did not expect such a big problem though.
Not to shove it in the face of all the people having this annoying issue, but I can confirm that with a fresh install everything is smooth and I haven't experienced any "big" bug as of yet. The phone seems even faster than with Oreo.
To be honest, besides the long process to reactivate the app of my bank, I don't even mind resetting all my apps every now and then, I noticed that it preserves battery life and performances. But I do understand that this may not be an option to some of you...

TechIntrigue said:
Just curious, why wait for the customized UK version? Does that have any benefits over the other firmware releases?
Click to expand...
Click to collapse
TBH, I'm not so sure, about either. Having read yesterday that the Singapore fw only has the Amazon app as bloat I'm going to install it today.
EDIT: Going back to Oreo as Substratum doesn't work without root.

Has anyone affected managed to do a full reset ?