Related
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk
Got two brand new OnePlus two's a day apart probably from the same batch.
On first launch it always got stuck on the checking connection
Tried both with
Vodafone lte
EE lte
bt hotspot
Vodafone hotspot
Multiple restarts did nothing
My guess was that some initialisation step happened at the factory and something funky was in the cache or data so I factory reset both devices (one day apart) and that solved it for me.
. After the reset and booting up it ran the updating android process which it did not before and then it worked flawlessly connecting to the networks
Hope this helps anyone and hope OnePlus fix this!
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Yep
dansou901 said:
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Click to expand...
Click to collapse
Same.
Sent from my OnePlus 2 using Tapatalk
Theshawty said:
Same.
Sent from my OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
LOGMD said:
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
Click to expand...
Click to collapse
Unlocking the bootloader wipes the entire data partition.
Yeah, I'm willing to bet .02 fixed it.
Sent from my OnePlus 2 using Tapatalk
My OP2 is from de 4th of september batch, i´m from Portugal and had the same problem! Resolved after the bootloader unlock.
I had this problem, skipped that step, updated to 2.0.2 and did a factory reset.
It was virgin again and ran flawlessly without this error.
So this was a 2.0.1 bug.
Same for me, skipped and everything went smooth.
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?
I have an old 6P that I haven't used for a few months. Noticed it was running slower than usual. Deleted apps, a few pictures, and rebooted it. Still slow.
Wiped the cache, when I woke it up it asked to unlock before continuing to screen. Proceed to connect the dots...which I've been doing for a day or two now.
Some reason it doesn't accept my password, it keeps saying wrong pattern even though I've been using it for a day or two.
Any suggestions? 8.1. updated this week.
If your rooted and have twrp can always try this. Kind of strange don't know how erasing cache could change your security. Did you update from Nougat to Oreo? I always do a factory reset especially when upgrading to a new Android version . Avoids possible issues down the road . ?
Exodusche said:
If your rooted and have twrp can always try this. Kind of strange don't know how erasing cache could change your security. Did you update from Nougat to Oreo? I always do a factory reset especially when upgrading to a new Android version . Avoids possible issues down the road .
Click to expand...
Click to collapse
8.0, then updated to 8.1. Still pretty slow, so rebooted. Still slow. Deleted stuff. Cleared Cache. Now some reason it doesn't take my pattern...which I used all day. So confused, legit feel crazy.
I rebooted it and now it won't recognize the pattern on boot. It's saying it's going to wipe it after X number of attempts.
I actually got rid of twrp after 7.1.1 fearing it might've caused issues w/ 8.0 OTA...
2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.
Well, @thesomnambulist after using speed reading techniques to carefully read that foreign policy and about 12.2 seconds there Ali I immediately inclined to tell you that your phone is not bricked. Message me.
thesomnambulist said:
2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.
Click to expand...
Click to collapse
Did you get the Essential resources & services updates last week via Google? Several people on the news forum threads related to the Android 10 update have also experienced very slow phones. Could it be related? Eg conflict with another app or the network you are connected to etc?
Though yours could be hardware issue.
At the time it happened, I was on 8.1, and not taking any updates. I'm leaning towards a a hardware issue since it persisted past a wipe and re-image on stock Android 8.1, Lineage OS 16.0, and stock Android 10.
I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk
samep said:
I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk
freshlysqueezed said:
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk
samep said:
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I would suggest no root then.
Sent from my PH-1 using Tapatalk
That's interesting, as I was initially rooted with Magisk as well, using Novo launcher. I'm not sure either of those are related to my issue though, since I've installed LineageOS without root or Novo launcher as well as stock Android 10 without root or Novo launcher, and the problem has persisted with all of them. Essential support has been absolutely no help, and as much as I liked this phone, I will not be doing business with them again simply because of their attitude in responding to me. That being said, I think I'm going to try to wipe everything manually, and go through the flashing process one partition at a time, and see if I can get anything working.
Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-snLbLs: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.
thesomnambulist said:
Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.
Click to expand...
Click to collapse
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons. Maybe that's ok but wiping partitions in another Android version may throw those errors?
Maybe our problems were similar with Android 10? I was using Magisk 19.3 and waited it out for 19.4 but I likely should have been on Canary build or switched immediately to Magisk 19.4 Slowdown with Nova until I couldn't launch apps anymore. With QuickStep 10, I only got to the point that I couldn't launch apps. Either case, reboot was a temporary fix that would restore UI speed.
I eventually realized I couldn't update BusyBox module with Magisk 19.3 so I updated to 19.4 through beta channel. Besides, I was having a similar issues getting to a point that I couldn't launch apps and having to reboot even with the QuickStep 10 launcher. BusyBox module updated without issue after Magisk beta update.
I'm hoping other issues may be resolved. I know I read many were using Canary build for across Android Q beta builds.
I'm just getting started with Magisk 19.4 so I may have more to add later. In your case, have you Android 10 again and see if the recovery wipes are still returning errors? If my phone doesn't improve, I may be upgrading sooner than expected. But there is a spare unlocked Essential PH-1 on my account now.
Sent from my PH-1 using Tapatalk
samep said:
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons.
Click to expand...
Click to collapse
That's a good question. I don't think this is the case, as part of my flashing process was to flash the bootloader (for 8.1) to both slot_a and slot_b, neither of which had any errors. I believe this means that I successfully downgraded to the older bootloader (assuming that it changed in 10). I know very little about filesystems, but the error message I'm getting appears to be some kind of conflict between ext2 and f2fs. At one point in this process, I know I formatted the partitions in TWRP, and I wonder if that formatted the userdata partition with the wrong filesystem. All of that being said, I have my doubts about whether the slowness is at all related to the userdata partition, as a reboot does nothing to help. The thing that really makes me think it's not software related is that the boot animation is extremely slow, and has been regardless of what rom I have installed.
@thesomnambulist, Are you confusing the boot.img with the bootloader?
ktmom said:
@thesomnambulist, Are you confusing the boot.img with the bootloader?
Click to expand...
Click to collapse
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.
thesomnambulist said:
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.
Click to expand...
Click to collapse
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel
ktmom said:
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel
Click to expand...
Click to collapse
Awesome! Thanks for that clarification. I'm not new to Android, but I have a lot to learn!
It's been more than 2 days since upgrading Magisk to 19.4 beta on Android 10 for me.
No slowdowns or freezes. Magisk Log appears error free since update but date changed from 09-24 to 10-29? Maybe not a MM-DD date?
The last error only showed the apps I was last running before it wouldn't launch another app. But did note: beginning of crash...
Anyway, my data was kept from the OTA update from Pie to Android 10, including Magisk 19.3 until beta update. Only issue appeared to be the need to update Magisk through beta channel or switch to Canary. I said I'd have more to say later.
Next step is to switch back to Nova beta launcher and see if that remains fluid and doesn't bring back any slowness I was experiencing before the crashes. Hopefully no slowness and crashes have ceased.
Sent from my PH-1 using Tapatalk
new screen
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.
blap017 said:
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.
Click to expand...
Click to collapse
I'm not thinking my issue was the display but using the wrong Magisk version for Android 10. This issues weren't present in Pie.
Initially I did suspect Nova launcher because the app switcher was slow and Nova just lagged until I couldn't launch apps. Stock launcher wasn't so slow but eventually I kept getting to a point no apps would launch. Magisk log did record one crash but only showed the apps I was trying to launch.
Updated Magisk and the issues were totally gone with the stock launcher for nearly 3 days. Not that I saw any issue but switched back to Nova beta launcher. Not long after that, the phone did a soft reboot (SystemUI reboot). I didn't give up on Nova but stuck with it anyway. It's been fluid since and Magisk log is clear.
Not sure if you meant my phone or OP. But consider it an update on my issue. My display glass is pristine and phone hasn't been dropped. Maybe displays go bad but I've never lost one or had it go bad.
One last issue I had with Android 10 on stock ROM, I posted my simple solution here:
https://forum.xda-developers.com/showthread.php?p=80434297
I haven't had anyone issues with Nova beta launcher since I posted last in this thread. Happily, I think all issues are resolved for me now!
Sent from my PH-1 using Tapatalk
I can tell you that "formatting data" is the only option to fix the issue that slow boot happens after system upgraded.