This just showed up this morning, automatically downloaded and I installed. Not Marshmallow but it is the June security patches. I haven't seen any other changes they've made and the Samsung version page hasn't been updated for the versions for these security releases either.
As for the delay of Marshmallow, I suspect it's because of the bug that was found during the upgrade where users are locked out of the phone. Working in a software development shop myself, my guess is AT&T may be waiting for this to be fixed by Samsung, who would then push another build out for them to work with. I could be wrong, but that's my sense. Personally, I'd rather wait for that fix than have to deal with a workaround (disabling the fingerprint reader, etc.) or risking being locked out. Hoping for sometime this summer, but we'll see ...... anyone have any contacts on the inside that may be able to hint at something???
mattsternc said:
This just showed up this morning, automatically downloaded and I installed. Not Marshmallow but it is the June security patches. I haven't seen any other changes they've made and the Samsung version page hasn't been updated for the versions for these security releases either.
As for the delay of Marshmallow, I suspect it's because of the bug that was found during the upgrade where users are locked out of the phone. Working in a software development shop myself, my guess is AT&T may be waiting for this to be fixed by Samsung, who would then push another build out for them to work with. I could be wrong, but that's my sense. Personally, I'd rather wait for that fix than have to deal with a workaround (disabling the fingerprint reader, etc.) or risking being locked out. Hoping for sometime this summer, but we'll see ...... anyone have any contacts on the inside that may be able to hint at something???
Click to expand...
Click to collapse
I don't mind getting locked out as long as I get Marshmallow
If I am out of the country, i can download via OTA this update ?
Im already in Europe and OTA say "Current software is up to date"
I have baseband version: G900AUCU4COI5
Related
Hello everyone,
I have question about 4.4.2. This night I went to settings to check if there is os update available and after half year maybe i can update again but now to 4.4.2 KitKat.
Can you tell me if it's good idea to update to 4.4.2. because i've seen some people are writing online about 4.4.2 issues...? Does this mean for all devices or?
I did not use any custom rom-s, and didn't do any os modifications, even i didn't "root" it.
Currently it is using 4.3. android and everything works well, but as you may think i'm pretty curios about 4.4.2 and i don't belive i can ignore that but i just want to know about some problems if any..
I repeat, it is offical update, not custom.
Thanks in advance
Perica
OMG. I've done update last night and i have these issues now:
- overheating of device (back,bottom) - with time it is heating less as i can see..
- 3g is disconnecting every half second
I'm now trying to fix these issues but as i can see i will now need to use custom rom
:crying:
Just to confirm that there is no overheating anymore. And 3g is now working because of some other not important reasons.. it was nothing to upgrade. I didn't do anything and now everything is fine. Overheating was because of inital initialization only i'm thinking. Anyway, even i didn't test it fully i didn't had any other problems and i can confirm that upgrade is fine.
What is the latest official firmware for the Samsung Gear Live?
I've been searching all over these forums for the Samsung gear live, and all over the internet also. I just bought a gear live off of Amazon for $100 and it's supposedly new. It currently has:
Software version: 5.0.1
Build Number: sprat-userdebug 5.0.1 LWX48P 1627902 dev-keys
Android Wear: 1.0.5.1627902
Google Play Services: 6.5.90 (1610726-534)
1) Is this the latest firmware?
2) Is this official firmware? Developer Firmware?
3) Will I get Updates on device? (Says up to date currently on the watch when I try to update on the watch)
Thank you so much for any help you can give me!
If you didn't figure out till now then read below
No this is not the latest firmware
The latest is 5.1.1
Connect the watch to your smartphone and then check for update on your watch(your phone should have internet connection)
You may need to use the gear live restore tool to change to non dev firmware (read the thread, don't use the latest version of tool)
Current:
Wear: 1.3.0.2160025
Play services: 8.3.01 (2385995-534)
Os: 5.1.1
LCA43
Thank you so much guys for all your posts. I used version 2 of the Samsung Gear Live Restore Tool to flash my watch back to stock settings, then used the normal updates via OTA on the watch.
I used the download link and the video from this post:
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
The video was step by step and super easy to follow ( Thanks Tom! )
I was in the same exact boat. $100 new from Amazon and had the same exact Software version, Build Number, Android Wear, and Google Play Services as the original poster. Went through the same steps, however I had to fight my computer a bit on the drivers.
In case this helps anyone else: I'm on Win7 64-bit. The first hurdle was getting a microUSB cable that worked (the USB multi-dongle I was trying to use turned out to be crap). Until I got a better cable, the Gear Live was not getting recognized by my computer at all. When it finally did, the drivers weren't getting set up correctly. I went to Device Manager, found the unknown device, right clicked and hit Update Driver Software (see about the 5:30 mark in Tom's video). I had two problems here:
1) My computer initially recognized the device as "Android Composite ADB Interface". That doesn't seem to work, make sure sure it's just "Android ADB Interface", NOT Composite. When I ran the driver check in the Gear Live tool, the device was now finally showing up for the ADB check.
2) But it wasn't showing up for the Fastboot check. To fix that, I had to GO BACK INTO DEVICE MANAGER after the ADB check, while the watch was in bootloader mode, find Android Device (or something like that, I forget what it was called), and again hit Update Driver Software and select the Android ADB Interface again. Once I did that, everything else in the video and Gear Live tool worked flawlessly.
I also wound up restoring the Gear Live watch to stock (option 6 in the tool), and it's downloading the OTA software update now. I'll post here if I hit any other snags.
Thanks again for posting this. Definitely helped me out.
EDIT: Note that if you go the OTA route, you're going to have to do multiple updates to get from the stock version up to the most current version. For example, stock starts out at 4.4W. It won't update from that all the way up to 5.1.1 in one shot. It'll do it in increments and take 3 or 4 updates. A little time-consuming, but otherwise I've had no further issues.
ROM History: http://forum.xda-developers.com/wiki/Samsung_Gear_Live
EDIT: Updating finished, here's the result:
-- Build Number LCA43
-- Android Wear 1.3.0.2160025
-- Google Play services 8.4.89 (2428711-534)
-- Android OS 5.1.1
I've never used my mac to do anything like this. What program do I need to open the gear live tool in, it's a .sh file and just opens in notepad. Thanks
would this lack of OTA updating ability cause the basic programs (Maps, google play music, etc.) not to work? Why is Samsung completely oblivious to this issue?
I have the sprat-userdebug 5.0.1. I'll be using this thread to fix it, I hope. But I cant get most of my apps to work on the watch. Hoping this will resolve it.
Thanks.
OTA now provided to convert from dev-keys to release keys
Today we are rolling out an OTA update to "sprat" Android Wear devices from Samsung that were stuck on a very old LWX48P firmware and old Google Play Services. These devices were sold with a non-standard "dev-keys" firmware, whereas normally devices use "release keys" firmware. dev-keys devices do not receive updates for anything. We have added a special OTA update that converts the LWX48P devices from dev-keys to the proper release keys LWX48P, and that will then allow the OTA update system to bring the watch completely up to date.
For users, it will take a few days for the update to be made available to everyone. After applying the update, you will need to factory reset and pair the watch up again, and then it will apply the latest updates that were previously skipped.
For developers, you will need to wait for users to apply the update and then you should see a drop in the number of old sprat devices showing dev-keys and old versions of Google Play Services. With this update, any user will have an easy to use path to get back to receiving regular updates.
See more discussion about this in my G+ posting ... plus.google.com/+WaynePiekarski/posts/izipAZnd56C
I am having issues with firmware ending bra5 my data connection keeps on dropping and I have to turn on and off airplane mode. Can I downgrade to bql5? I think that's what I had before updating. I am on Verizon. Please help. Thank you
Become a member of the world
Nope, you can't downgrade the bootloader
Caliskyhigh said:
I am having issues with firmware ending bra5 my data connection keeps on dropping and I have to turn on and off airplane mode. Can I downgrade to bql5? I think that's what I had before updating. I am on Verizon. Please help. Thank you
Become a member of the world
Click to expand...
Click to collapse
FWIW, I'm on 3BRA6 and have had some instability on WiFi connection disconnecting.
Regarding "downgrading", generally you can as long as to older version you want to go back to has the same bootloader.
In this case, unfortunately 3BRA5 has the new V3 bootloader. So we'll just have to wait for the February security patch and hope that fixes the issue.
So I installed the new Feb security patch on Verizon note 8, it seems to be working fine for now. Thank you for the help.
Cant downgrade but you can upgrade. Can install BRA6, BRA8 or BRA9.
Caliskyhigh said:
So I installed the new Feb security patch on Verizon note 8, it seems to be working fine for now. Thank you for the help.
Click to expand...
Click to collapse
Welcome. Come back in a couple of days and let us know how it's working.
So it's confirm the Feb Verizon security patch update fixed the lte/wifi connection issues. If your having issues with let or wifi on Verizon note 8 go ahead update.
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Yes, just download the update and flash it yourself. It isn't very hard and the effect is the exact same as an OTA update so it doesn't void your warranty.
Better stay in oreo cause this latest pie
updates bricked my wifi and sd card
8i advice you to keep the phone with oreo.
ntzntz said:
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Click to expand...
Click to collapse
Buna seara / hello,
I think you should manually update. Follow this
https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774/page99
I have a TA-1046 dual SIM, international version (yours is probably the same).
I was stuck first on Oreo 8.0 in April and I had to manually update to 8.1. After that I got OTAs without any problems until the Pie update.
In September I had to manually update to Pie, but since then I got every OTA.
Everything works fine, no issues with WIFI. I do not use an SD card. Pie is better than Oreo and you need the latest security patches.
Mult succes.
It's interesting that some people don't have any issues with last updates but quite a lot of people have the same issues i have,today i tested my friend's phone and has the same firmware like i do but yet no issues for him
Btw: before you upgrade, august is last version can be unlocked
I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!
yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.
They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now
Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.
And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....
Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.
Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?
It has been nagging me since last few weeks, no solution apparently
New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.