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 ?
Related
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:
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..
DOK2 all stock firmware here.
Got my phone back in december. My phone has been chugging alone fine until yesterday. not sure what happened but the lock screen takes minutes to come back. I tried doing a factory reset via software and when I did that the phone was still sluggish. Tried a stock recovery reset, and afterwards when i tried signing into my account and connecting to wifi at the initial setup the phone just rebooted back to the start screen again which i thought was real odd. It's currently restoring apps from the app store right now and it intermittently reboots itself while doing stuff. all while it's completely stuttering if i try to use it...
Is my phone starting to have internal memory failure? no SD card in the phone at the moment.
Should I try reflashing the DOK2 firmware via odin and then doing a reset again? Is that even possible with all the restrictions?
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Check this thread for a workaround. I use an app to keep my phone from going into deep sleep.
http://forum.xda-developers.com/showpost.php?p=64584244&postcount=39
dtrinh4000 said:
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Click to expand...
Click to collapse
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Bruce lee roy said:
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Click to expand...
Click to collapse
Did a factory reset and cleared cache, reflashed stock DOK2 from sammobile website using odin, cleared cache. things were going a little bit better at first but now just stuttering all over the place and randomly rebooting still. I only have very few apps downloaded, including facebook updates, instagram, all the samsung and google crap that forces updates...
Also want to add that booting into recovery takes a very long time, longer than i've ever noticed it taking... 7 min+ sometimes it will say "installing system updates" with the android guy chugging along, other times it will just have the android guy chugging....
Is there anything else I can try? Is there something I can test to verify that it's a hardware issue and not a software problem, like a flash memory checker?
This phone is out of warranty, and knox has been tripped so I have very limited options here. Would the Tmobile store let me do an exchange for a fee?
bump... anyone? am i really screwed?
dtrinh4000 said:
bump... anyone? am i really screwed?
Click to expand...
Click to collapse
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
cuteman said:
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
Click to expand...
Click to collapse
I do get some touch wiz crashes and random app crashes . since I'm on dok2 is there any other rom or recovery I can flash ? Or so some super duper erase method? I'm pretty much ready to cut my losses and sell it for parts on eBay.
i'm not alone it seems
http://forum.xda-developers.com/note-4-tmobile/help/note-4-major-slowdown-bugs-boot-loops-t3311297
http://forum.xda-developers.com/note-4-tmobile/help/looping-screen-t3319204
http://forum.xda-developers.com/note-4-tmobile/help/reboot-shutdown-wont-removing-battery-t3316875
I am having same issue. Was running stock until 3 days ago, when I got fed up with the stock reboot and slow-down. I guess it's time to save up and get a new phone.
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
dtrinh4000 said:
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
Click to expand...
Click to collapse
Well, fool me once.... Having spent $800 on a phone that broke in just over a year, hell would have to freeze over before I give Samsung any money again.
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Login into this website using your Samsung account
findmymobile.samsung.com/mindex.jsp
Find "Unlock my device" section
And make sure your device is connected to the internet then unlock you device
GreenXSI said:
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Click to expand...
Click to collapse
On the MM build, after a reboot you have to use the pin but subsequent times will be fingerprint, I have no idea why they did this. Sorry that happened to you, I have no idea how to get around that other than to keep searching, someone else had had that happen I'm sure.
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Douglas333 said:
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Click to expand...
Click to collapse
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Rats! Catch 22...
MrMike2182 said:
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Click to expand...
Click to collapse
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Douglas333 said:
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Click to expand...
Click to collapse
You need to learn to "manually" back your stuff up yourself and don't rely on any programs/apps to do it...
There's seriously nothing the dev community could do because for 1 it's not the right way to go about this because if someone's phone is stolen or whatever basically they'd be able to come to XDA-Developers and find a way around the phone being locked for 2 that's definitely not what devs do, we don't look for ways to break into a phone or circumvent the security. You should have backed up anything you knew was important, simple as that .. You need to factory reset at this point. Sorry.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.