Hi folks, heads up: I've just received a software update. I was happy to install it, but it didn't work
The phone rebooted a few times, and now I'm stuck in Download Mode. Any ideas?
Yep same thing happened to wife's phone. Used ADB to boot phone into fastboot, attempted to sideload the latest Nokia 7.1 OTA I could find. Complains about timestamp being older than current build and cancels sideload. Was hoping someone could save me and upload the latest Nokia 7.1 build. Otherwise will likely have to send it in for repair which seems overkill for the situation.
I sent it in for repair. Bought a Sony Xperia XZ2 Compact (can return it within the month).
Mine did this on the Feb update too and I had to send it in to Nokia warranty for repair. Took exactly one week to get back to me. Exact same thing, locked in Download Mode. I got the same phone back, same IMEIs. Since it came back it has only updated to the January build and says it is up to date.
So. The February update is faulty I should get it back tomorrow, let's see...
dryhte said:
So. The February update is faulty I should get it back tomorrow, let's see...
Click to expand...
Click to collapse
This Feb patch is horrible. Performance has gone down. Now, in recents phone starts to stutter when i swipe through apps. They can't even fix the bugs.
Sent from my CTL_sprout using XDA Labs
dryhte said:
So. The February update is faulty I should get it back tomorrow, let's see...
Click to expand...
Click to collapse
Is there anyway to downgrade this to oreo ?
Sent from my CTL_sprout using XDA Labs
mayankjet said:
Is there anyway to downgrade this to oreo ?
Sent from my CTL_sprout using XDA Labs
Click to expand...
Click to collapse
don't think so, but I'm perfectly happy with Pie, it's just the February patch that was a bit of a problem
In fact, I got my phone back, and it was on original Pie (= december patch), and it downloaded the January patches straight away - there's no trace of the dreaded February patches so I think they withdrew them.
dryhte said:
don't think so, but I'm perfectly happy with Pie, it's just the February patch that was a bit of a problem
In fact, I got my phone back, and it was on original Pie (= december patch), and it downloaded the January patches straight away - there's no trace of the dreaded February patches so I think they withdrew them.
Click to expand...
Click to collapse
I feel like with a bit more optimisation it could be even smoother. Animations are not as smooth as they should be.
Sent from my CTL_sprout using XDA Labs
I'm still on the januari update, since I received my phone back. Wondering what's up with the februari patches - and hoping the steady stream of updates hasn't stalled indefinitely.
So, solution to this problem is sending back for repair? My girlfriend got same problem today :-/
Chivas610 said:
So, solution to this problem is sending back for repair? My girlfriend got same problem today :-/
Click to expand...
Click to collapse
Yes, for me it was. (note: my issue was that the February update sent to phone to download mode)
I received March update for TA-1100 today. After update and rebooting phone stuck in download mode. I can't enter recovery, I can't even power it off. Any suggestions, please?
dryhte said:
Yes, for me it was. (note: my issue was that the February update sent to phone to download mode)
Click to expand...
Click to collapse
I delivered back for repair. I don't know which update it was, but seeing problem reported with March also, it might have been that one.
Guess the solutions the next months must be TURNING OFF updates.
damijanp said:
I received March update for TA-1100 today. After update and rebooting phone stuck in download mode. I can't enter recovery, I can't even power it off. Any suggestions, please?
Click to expand...
Click to collapse
Well, as you can read above, we all sent the phone for repair. Don't know if there are other solutions.
Chivas610 said:
I delivered back for repair. I don't know which update it was, but seeing problem reported with March also, it might have been that one.
Guess the solutions the next months must be TURNING OFF updates.
Click to expand...
Click to collapse
I received the March update today and all's well. (I was a bit surprised that I didn't actually get the option to not install it, it downloaded and started installing right away, but after a tense 5 minute reboot, the phone is fine)
dryhte said:
Well, as you can read above, we all sent the phone for repair. Don't know if there are other solutions.
Click to expand...
Click to collapse
I've sent it today, too.
Got the phone back, now with Android 8.1 installed
Chivas610 said:
Got the phone back, now with Android 8.1 installed
Click to expand...
Click to collapse
How did you go back to Android 8.1, you did it or you took it to the technical service?
Related
Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.
Awesome! Is this the same 108 build that went out to beta testers?
Does it include the battery optimization that was mentioned some time ago?
***
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.
Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?
Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk
DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.
Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.
revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!
Any word on android 8
Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful
hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.
mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.
mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!
mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?
mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage
mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.
Hi, A lot of people are having issue regarding security of device as you cant change your pin and it wont let you enter your pin by showing wrong pin. You cant even have any security after doing a factory reset.
I have done everything to fix it , even took it to samsung repair center, still no success so I have sent it to samsung warranty today.
I have done these things to fix it but nothing worked.
1. Tried online samsung and google "find my phone" service" to fix it as it is shown on some sites for older phones.
2. Reset the phone through recovery.
3. Install fresh firmware through Odin. Then installed both beta versions.
4. Installed orignial firmware mine was VAU.
5. Installed the first firmware of s10 plus. With Nand reset and partition using PIT file.
6. Took it to samsung, they tried 2 different firmwares to fix it but all in vain.
In the end Samsung told me that it might be issue after security patch done for screen protector. They cant do anything at the moment and I have to wait for a fix through update but I have sent my phone to warranty.
I posted this issue in Q&A last day after having issue. But now I can see There are a lot of people affected by this. In my opinion it is Beta 2 issue.
Once you encounter this issue, you are helpless until samsung fixes it. Until then just keep your data, no need to do factory reset or new firmware, as it wont do any help.
What?... Never had any of these issues dude
twoxa said:
What?... Never had any of these issues dude
Click to expand...
Click to collapse
I also got this first time. It is very frustrating and I spend 7 hours to fix it but nothing worked. Until now i have seen 5-6 people who are facing this issue after beta 2. More might come.
I'm also facing this problem, hope Samsung fix this ASAP.
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
madvinegar said:
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
Click to expand...
Click to collapse
I sideloaded it.
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
madvinegar said:
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
Click to expand...
Click to collapse
I did rolled it back but didnt work for me. my issue is persistent and even samsung service centre could not fix it. I gave my phone in warranty because I am not sure how much samsung will take to fix this issue and they might be able to fix it. Lets see what samsung will say.
am not having any of these issues on S10+ Beta 2
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
bomp306 said:
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
Click to expand...
Click to collapse
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Does this have anything to do with the recent update in the biometrics (fingerprint issue).?
I cannot understand why this bug was not seen right after the update to Beta2, but only after 3-4 days...
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
The good thing is that this bug affects also the ones who officially enrolled to the Beta program, so this means that Samsung must be working to release a fix. At least I hope...
kazim.asghar said:
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Click to expand...
Click to collapse
I'm on latest android 9 stable via ODIN but the problem with biometrics and pin lock keep in the phone, I did every wipes with no results
Hotfix rolling out now OTA
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
AshishV95 said:
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
Click to expand...
Click to collapse
It's already shared in the appropriate thread.
Intratech said:
Hotfix rolling out now OTA
Click to expand...
Click to collapse
Fixed!!
Just need to restore all my apps again now..
should change the thread to SOLVED now that samsung has released a hotfix for it
bomp306 said:
Fixed!!
Just need to restore all my apps again now..
Click to expand...
Click to collapse
Is it fixed? Can you change pin code?
I flashed it and I have absolutely non of the issues you're having. I have an unlocked S10+ on Verizon and I'm running the ZSJF build
My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?
Yes
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?
old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?
old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.
Do I need to root my phone before manually updating using the OTA file?
speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No
Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal
From Orange France is 036, from Google store is 037
Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
My wife uses 3-button navigation (I use gestures). She's unrooted and using Nova Launcher. She said she hasn't had that issue.
swieder711 said:
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
Click to expand...
Click to collapse
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
almahix said:
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
Click to expand...
Click to collapse
Are you running any magisk modules? I thought that might be related to what I am seeing.
swieder711 said:
Are you running any magisk modules? I thought that might be related to what I am seeing.
Click to expand...
Click to collapse
Magisk for root but no other modules
I think it's not magisk related
And I'm also experiencing this on gestures
Swiping up sometimes just does nothing and is really annoying
Edit: stock on Jan update
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
superman25 said:
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
Click to expand...
Click to collapse
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
almahix said:
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
Click to expand...
Click to collapse
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
roirraW edor ehT said:
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
Click to expand...
Click to collapse
I'll try that way next time I can't update.
My 6 will do that. They just stop responding. Myself I don't need to reboot though. Either I can wait for a few seconds and they'll start working again, or at most lock then unlock the phone.
I had the same issue all the time on December update. A reboot would fix it but I have not seen it all on January update..
I had that problem with December's build, but so far it hasn't happened with January's.
Using 3 button myself on Jan update. Also use Nova and have had no issues. It was a clean install though.
I have a OP8 with a custom a11 ROM on it that 3 button navigation has worked flawlessly on. I upgraded it to 12 over the weekend and have had the buttons lock up a couple of times since. So it would appear to be a a12 thing, and not just a a12 on Pixel issue.