As i've wrote in another Thread (Bootloop at M1D64T), my SWR50 has this behaviour since this Update.
So, i've manually rolled back to Lollipop - discribed in the Thread " How to Fix SWR50 with working Fastboot".
Now, everytime the Watch comes at the Point to Update from Lollipop to Marshmallow, it's endet in the Bootloop with the four Dots...all Updates to higher Lollipop-Versions works like a charm...
Another strange observation i've made when i tried to change to the chinese Fitware....all went fine, but i don't like these Software and rolled back to AW. The Fitware put my Watch back to LDZ22D.
The Watch seddle up, all was fine and after a while the Watch want performe an Update. At the the end from the Update, the Watch booting, but it don't show the circling Clock, no, the four Dots come up, but only for two seconds, then the Watch stays in Recovery...no warning about a failed Update...After i've booting manually from Recovery to System, all runs good and the Watch was on LDZ22D.
So at this point, it can't be the Update to LCA43 by OTA, the Watch says im at the actually system...
Now i will try an manually update to LCA43 and ignore the Update Message to MM....
I'll hope, Sony release an Update to correct this Issue...
Related
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.
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.
Hi all. At 4:20 AM PDT (the notification sys 8:20AM for some reason) this morning (June 12) my Note 4 buzzed and woke up and let me know there was a software update available. Any idea what this is?
I didn't install the small security update last month yet, is this just that update trying to be more forceful (the notification will not go away)? Or is it a new update?
Try it, and let us know what it is !
I didn't install last month's security update myself for the fear of losing that slim chance of an unlocked bootloader and root..lol
I haven't received a notification about an update this month..would you happen to have a description of the update?
Well, the notification wasn't going away and I accidentally hit continue and it rebooted and installed whatever it was.
Took it's sweet time installing and then optimizing apps, and as far as I'm aware nothing changed. Same baseband, same kernel, same build number (LMY47X.N910AUCU2DOI3) according to About Device.
Also my phone is starting to show me the same annoying screen that started appearing when the security update came out saying to connect to wifi to download another update (whatever update was installed today, it downloaded itself via mobile, not wifi).
So I am rather confused as to what the 'update' I installed was.
I have, apparently, one of those sw3's that will not accept the MM OTA so that the watch will work after is successfully installs. I am having to reinstall the LCA43 ROM in order to get the watch to work. While I would like to have MM, I can't seem to find the right ROM to install and XC is no help in either the software repair or update. The issue is when MM is on the watch, it continually stops at the 4 dots or symbols and never goes any further. I am using Ubuntu to connect to the watch for repair.
Is there a way to stop the OTA updates while still being connected to the phone via BT? I was happy to get this watch going again, but was disappointed this morning when it tried to boot in MM without me installing it.
Edit: This may be resolved. I installed a different ROM yesterday, 5.1.1.2, and it did not automatically try to upgrade last night so I may be good to go.
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?