Hi. I just installed the Android 7.1 DP2 on my Nexus 5x. Before the install started, this message popped up. After the install the phone worked properly. I restarted the device just to see it the warning would show up again and it didn't. The phone is not rooted. Just stock android. Also I don't remember changing anything major to the settings. Should I worry about this?
Its normal. Just ignore it.
Related
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time.
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
specd_out said:
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
Click to expand...
Click to collapse
my phone is still on 8.1 and a check say's up to date, I have downloaded 9. ppr ota , would like to know before i side load, have you got root back ? I use magisk .
I have not attempted to get root back.
Did you have TWRP? Honestly, I'm in a situation where I'd like that to happen. Unfortunately I don't have access to my PC and would like to take the final OTA to Pie, but I'm rooted with Magisk, and.have TWRP installed, I'm worried about a bootloop.
I'm just trying to figure out if there is a way to force my phone to get the OTA update the normal way. My Pixel picked it up as soon as I manually checked for an OTA Update. My daily driver Pixel XL has been saying that I am up to date for the past 22 - 23 hours since the update went live, so I'm still stuck on 8.1.0. Does Google drip feed the update out in blocks based on IMEI to limit the impact on the download server?
So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.
I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again