Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
hbkekko said:
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
Click to expand...
Click to collapse
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Jammol said:
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Click to expand...
Click to collapse
I tried to wipe cache from settings, storage but didn't work. Yes I've unlocked bootloader but no root. Could this be the problem?
No, shouldn't affect anything just being unlocked. Now if you installed TWRP, that might cause this. I didn't use an OTA to go to the march update so idk if it might be at fault, I was on pure Nexus so chose to flash the factory image and haven't had any issues so far.
Sent from my Pixel XL using Tapatalk
Solved flashing the latest factory image via fastboot
Related
Issue resolved.
MiasmicTaco said:
This morning my Razr M received the latest OTA update. I was previously rooted with a locked bootloader (I know, bad choice).
I proceeded with the update but my phone massively screwed up: lost wireless, contacts malfunctioned, several apps failed.
I went through all the steps to clear cache, soft reset, hard reset, etc. Ever sense my phone has been stuck on the setup wizard screen stating "Please wait, this may take a few minutes". I left this morning at noon returned home at 7 and it is still on that screen.
Click to expand...
Click to collapse
Try using RSD to restore to the same version (4.4.2). I've gotten that wireless issue before, and I just had to format userdata and reinstall the update to get it working.
just roll back to orginal firmware by using RDS and after that,use OTA update
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
cswee1932 said:
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
Click to expand...
Click to collapse
Did you do a wipe when you flashed or just update? If you just did an update, I would try to reinstall and let it wipe the device.
Yup. I'm experiencing this as well. Happened to me twice yesterday. Maybe try a factory reset?
Sent from my Pixel XL using Tapatalk
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
I've had 3 reboots since jumping on Oreo. Did my update the clean way through a factory reset and flashing a factory image. Stock, unrooted.
humdrum2009 said:
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
Click to expand...
Click to collapse
Stock, updated via ota... Having 5 to 6 reboots per hour. Google is sending a replacement phone.
Maybe you have to do a factory reset.
Reason why i havent upgraded. Still on a rock solid nougat until google fix all this problems. Maybe 8.1 or so. Seem like reboot is a common problem with the pixel,. All thread about orea theres someone talking about his reboot problem in many different sites.
jerryhou85 said:
Maybe you have to do a factory reset.
Click to expand...
Click to collapse
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
sandibhatt said:
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
Click to expand...
Click to collapse
That sounds much like a hardware failure... :crying:
I had random reboots too coming from DP4 to FInal. No more random reboots since I flashed the factory images
Is 8.0 the version that is the start of the new OS updating system? I wonder if the partitioning is getting all screwed up? I think I'll stay on 7.1.2 for a bit longer till this gets ironed out.
Sent from my Pixel XL using Tapatalk
Stock, bootloader unlocked, Oreo by OTA, and 1 random reboot and 1 random power off
Sent from my sailfish using XDA Labs
Not gonna upgrade to Oreo.
Is there such a way?
nabbed said:
Not gonna upgrade to Oreo.
Is there such a way?
Click to expand...
Click to collapse
Just don't download the OTA till they send out a patch. That's what I'm doing.
Sent from my Pixel XL using Tapatalk
when i first updated to oreo and rooted it, i ran into the rebooting issues some of you are experiencing. i think the root of my issue was busybox. i did a clean install of oreo again the other day and rooted, but didnt put busybox on the phone. phone ran fine for a day, so i tried giving busybox another go. the reboot issues came back. hope this helps
Mine only reboots randomly if I have YouTube picture in picture enabled once I disabled it I haven't had any reboots maybe try to disable that
Just did the update a couple hours ago and so far so good. Picture in picture works too. Stock, GPE on VZW, no root or anything.
Sent from my Pixel XL using Tapatalk
Guys, anyone still getting random on persistent reboots on Oreo with Pixel (XL)? I'm doing my second factory reset atm and monitoring these two threads on buganiser - 1, 2. Basically people started getting reboots after upgrading to Oreo and one notable common thing is: 'Sense Key : Hardware Error [current]' which Google reps assigned to the threads read as hardware issue (probably with Toshiba's memory chips being prone to overflow/overload (?)). They haven't answered my question why is it only happening on Oreo though. I REALLY don't want to go through the warranty process again only to get a device with the same problem as I still believe it can be fixed in 8.1. Is there anyone who had similar issues that got fixed with the 8.1 Beta? Cheers!
I'm experiencing the random reboots too.
Oct. 8.0, Magisk, Root
I almost missed an alarm due to this, so I think I may go back to Nougat. Not only does it reboot, but it gets stuck in the boot screen. If I hold Power and reboot, it comes up though.
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Merky_21 said:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Click to expand...
Click to collapse
You want help without logs? This is a developers site not Magic kingdom!
new owner here..
I just received the S4, installed some apps, searched for updates, got the november update, installed it and it did a complete factory reset!!
Something wrong with the OTA update??
All I did was the update, it never asked me anything about a full wipe
common problem?
I read about this problem in spanish forum but we don t understand if it is a ota problem or something else.
Jakke102 said:
new owner here..
I just received the S4, installed some apps, searched for updates, got the november update, installed it and it did a complete factory reset!!
Something wrong with the OTA update??
All I did was the update, it never asked me anything about a full wipe
common problem?
Click to expand...
Click to collapse
I just checked my Tab S4 and it only has the Sep 2019 update and says that is the current update. No factory reset when that update was installed.
The november OTA caused factory resets for some users and isn't available anymore (lots of posts in german android-hilfe.de). I guess a new version without this problem will be available soon.
Spanish version here... For me, a recent update did a factory reset. I was really angry about that, but I think that was in September.
I didn't get a factory reset but I'm experiencing touch screen problems since the november update. Sometimes part (or whole) of the screen becomes unresponsive. Reboot fixes it so I suspect it is a software issue.
Mine to here in the states...anyone have any suggestions, not trying to reset
Happened to me.
yes, he did it to me in three firmware I tried....
(spain PHE, france XEF ,Greece)
I am surprised by the lack of discussion about the August patch. Has anyone tried it? Is it easily rooted withMagisk?
After the problems that I had with the July patch, I am hesitant about moving the August.
Installed and rooted my wife's P3 within a few minutes of release Monday. Factory image (no -w) method. Worked with no issues at all.
Just installed and rooted now (no wipe), and it's fine.
Completely forget to update until this thread. I just did my usual method. Restore images with Magisk Manager, do not reboot, OTA update, do not reboot, reroot with Magisk Manager to the inactive slot and then reboot.
Everything went fine.
I took the plunge thanks to the feedback here. Flashed, no -w. Forgot to disable Magisk modules before flashing. Thankfully no problem. Even have GravityBox running with no issues.
I've done the OTA update and it fixes the last month terrible battery life.
Back to 6/7h of screen on.
The rest I can't help.
sliding_billy said:
Installed and rooted my wife's P3 within a few minutes of release Monday. Factory image (no -w) method. Worked with no issues at all.
Click to expand...
Click to collapse
Same here.