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.
Related
It seems my phone is stuck on ALJC. I flashed the stock recovery via Odin and did a temp unroot, downloaded the OTA update. The phone rebooted and went to the stock recovery and appeared to be installing the update. Upon reboot, my phone was back in rooted condition (not sure if this is normal for voodoo unroot or not). This has happened twice. The first time it happened I had not noticed it, but now that it has sent a second update request to me today, which I used the same method only to discover that it doesn't seem to work. Now when I request an update it tells me no update is available. Suggestions?
Ignore this thread, I said screw it and just did it all manually.
So I had my phone rooted sometime around the point when the 4.1.2 OTA came out. I went back to stock recovery and a nandroid backup that I made before rooting. Now, about once a week, I get the notification that the update is available but it doesn't work. My phone reboots like its going to update, I get the android guy with the spinning graphic thing, then it reboots the same as it was before.
I tried searching but couldn't find a solution...if my searching skills suck just let me know
THANKS!
The update showed up on my phone and so I updated it after unrooting my phone, removing lucky patcher, freedom, sd booster, and so on. After downloading the update, phone rebooted showed it was updating then Error. Rebooted the phone then the update was no longer there, tried using System update but to no avail.
My question is.. how do I fix this for me to be able to update to the latest?
I'm getting a similar problem. However instead of doing what you did to unroot and such, I flashed the 2.17 via their recovery and now I don't get the prompt for 2.18 update at all.
Its confusing as to why its acting like this :/
I already removed all root applications and unrooted the phone then did a factory reset but afterwards it put me to one of its old build and wont freakin update anymore.. Any help regarding this would be very much appreciated..
I am open to rooting and manually flashing the latest build.. Problem is, I was a Sony user whom just switched to zenfone.. So i have no idea how to or what to flash on our zenfone 2..
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.
you haven't finished , actual OTA is 2.19.40.18
I haven't received that update yet. 2.18.40.12 was the older update and was the one I downloaded/installed.
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?