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
Related
Hi
Just updated my Tab after Kies informed me that there was a new version, but after the update, Kies is bluntly refusing to connect to the tab. Just says 'Connecting...' forever.
I'm guessing that Samsung has stupidly managed to update the firmware in the device to a version that Kies cannot talk to.
Anyone else have this issue. Until I get it resolved there will be no further updates on my GT.
The build no post update is: FROYO.XWJJ3
I've done all the usual things: restart pc, restart tab, reinstall kies, install kies on fresh machine, blah, none of which have helped.
Any idea's?
Interestingly, post update, the only thing that I see thats different is that Samsung has installed 'The Dark Knight' and 'Clash of the Titans' trailers on my tab (now deleted). Those two files make up the lions share of the 'update' that I downloaded. Cheeky blighters. 'Sky News' and Whsmiths 'eBooks' apps have also appears - very very cheeky - enough rubbish on the tab beforehand without Samsung adding more. The new 'Apps' cant be deleted either...
Nigel
Dones anyone has step by step tutorial how to update omnia 7 from nodo to beta2 mango ? thx in advance
I'm intersted as well what to do exactly.
This is what i did,
1. Flash you phone with Samsung Omnia 7 Firmware XXJL3 RETAIL UNITED KINGDOM. you should have v7004 installed.
2. Plug phone in to PC and check for updates with Zune, it should say that the Feb update is available, install this update. (if you have problems installing this, make sure your USB cable is connected to a USB port that is physically on the motherboard and try again)
3. Check for updates again, this should say that the NODO update is available, install this update.
4. Follow the instruction on THIS site to get the mango updates.
NOTE: When i tried this with the KC1 firmware, my phone would get stuck in a reboot loop when going through the instructions in step 4, i had no problems with JL3 firmware.
Anyone had any problems with Mango yet? Crashing, laggy, etc?
I'm curious, do most apps work with Mango? Or will they all disappear/fail to open once I update. Also, does this process/"restore.bat" delete data ie. game saves?
I'm interested in updating to Mango, but not at the cost of lost apps/saves either during the update or restore.
I have no crashes at all with mango, the OS is a a lot more responsive overall.
I have only brought one app on my Omnia, all i needed to do was go in to the marketplace and redownload and install it again.
Thanks for the instructions Duck!
I followed them to a 'T' (minus the firmware updates, my phone was bought unlocked and unbranded) and it worked great! All my game saves, apps, etc. were there and Mango runs smooth as silk!
The only downside (and the link mentioned this) was that Zune does not sync with my phone anymore. It requires and 'update' and once you try and get that update Zune errors ('Cannot find update file: blah blah'). So it looks like this currently Mango build prevents Zune syncing (although wifi might still work, I'll have to test it).
Download the Beta version of Zune HERE.
Awesome, that worked great! Where do you find this stuff?! Hah, thanks again.
I always get the timeout when it is restarting for the first time.
OS: 7.10.7712.60
Firmware:2424.11.3.1
Hardware Revision Number: 3.15.0.4
Radio software version: 2424.11.2.2
Radio hardware version: 0.0.0.800
Bootloader version: 5.3.0.4
Chip SOC versopm: 0.36.2.0
Available space: 2.49 GB of 7.39 - I deleted the music as someone in another thread suggested but no help.
Edit: Suspending the process and deleting the unneeded files worked for me.
does anyone know if you lose the Live Services activation key after the a Mango Update? thanks in advance
singularity0821 said:
(...)
Edit: Suspending the process and deleting the unneeded files worked for me.
Click to expand...
Click to collapse
Can you explain wait you did, please?
I'm stuck on "Restarting your phone...".
The phone reboots, waits on backup/download mode (bw image of phone linked to PC) and nothing else happens till .cmd gives a time out.
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#7&b4f563e&0&0000#{ca3d7387-f67b
-11da-bbec-8000600fe800}
SN: (...)
Name: (...)
KITLName: (...)
Manufacturer: SAMSUNG
ModelId: 4
Model: OMNIA7
MobileOperator: (...)
Version: 07.10.07712.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.03 seconds
Checking system requirements: Completed in 0.02 seconds
Downloading updates: Completed in 3.02 seconds
Checking system requirements: Completed in 0.02 seconds
Transferring updates: Completed in 1.84 seconds
Preparing to install: Completed in 14.13 seconds
Restarting your phone..
UPDATE: SOLVED! Uninstalled Zune and UpdateTool, rebooted, installed Zone and UpdateTool again, rebooted, updated phone.
Guys if there is an update for the 8.9 can you simply update over the air on wifi or do you have to update via a pc download?
Not checked my firmware version yet but suspect its not the latest version of honeycomb.
Ta.
I've only updated via PC i.e. using Kies but the option is there in settings.
just go to Settings > About device and hit Software update. you must have a google account and a samsung account and a working wifi connection. that's it
Thanks.
80% through my update now.
So easy only take few mins. :-D
Hey,
I bought a Nokia 7 Plus TA-1062 from China. After it arrived I installed the global android version using the instructions provider here. I then side loaded a 8.1.0 version with Security path from 1st of August. The phone is functioning fine in terms of ability to browse web/take calls/use camera/etc. - HOWEVER - during any of these updates I wasn't able to use any of Google's services (Play Store/Cloud login/Updates). It's just stuck on 'Checking info...' and sometimes notifies it wasn't able to connect.
When I look at the Google Play Services logs (using the *#*#426#*#* code) I see that the connection is failing constantly. I've tried reseting the cache/data of all related apps and the phone itself without help.
Anyone knows how to solve this? Why are the Google Play Services not working?
bob2016_123 said:
Hey,
I bought a Nokia 7 Plus TA-1062 from China. After it arrived I installed the global android version using the instructions provider here. I then side loaded a 8.1.0 version with Security path from 1st of August. The phone is functioning fine in terms of ability to browse web/take calls/use camera/etc. - HOWEVER - during any of these updates I wasn't able to use any of Google's services (Play Store/Cloud login/Updates). It's just stuck on 'Checking info...' and sometimes notifies it wasn't able to connect.
When I look at the Google Play Services logs (using the *#*#426#*#* code) I see that the connection is failing constantly. I've tried reseting the cache/data of all related apps and the phone itself without help.
Anyone knows how to solve this? Why are the Google Play Services not working?
Click to expand...
Click to collapse
I am also the Chinese version of Nokia 7plus, also found this problem, the message can not be pushed!
flashing gapps would solve the problem if you have a recovery installed, but since we cannot unlock our bootloader, you're ****ed
Sowa96 said:
flashing gapps would solve the problem if you have a recovery installed, but since we cannot unlock our bootloader, you're ****ed
Click to expand...
Click to collapse
Thanks for replying - I'm new to all this and would like to learn more -
1. What does it mean to have "recovery installed"? I'm able to enter the recovery console on boot via the power button+up volume key trick (that's how I sideloaded the 8.1 version), I'm guessing that's not it?
2. What does it mean to unlock the bootloader? how do you know if your bootloader is locked or not?
3. and probably most important - how do you flash gapps?? That's something that I'd like to try, maybe my phone is already unlocked by some sheer luck (doubt it since it came in a sealed box)
bob2016_123 said:
Hey,
I bought a Nokia 7 Plus TA-1062 from China. After it arrived I installed the global android version using the instructions provider here. I then side loaded a 8.1.0 version with Security path from 1st of August. The phone is functioning fine in terms of ability to browse web/take calls/use camera/etc. - HOWEVER - during any of these updates I wasn't able to use any of Google's services (Play Store/Cloud login/Updates). It's just stuck on 'Checking info...' and sometimes notifies it wasn't able to connect.
When I look at the Google Play Services logs (using the *#*#426#*#* code) I see that the connection is failing constantly. I've tried reseting the cache/data of all related apps and the phone itself without help.
Anyone knows how to solve this? Why are the Google Play Services not working?
Click to expand...
Click to collapse
Hello, i have this 1062 chineses with global ROM too, this code to Google services log work to me but the problem im facing now its only"device uncertified" and NFC dont work, also OTA dont work, OTA Gave me updates until May, after this i did updates until Aug by SD
Hi all,
How are you?
I have spent soooo many hours trying to upgrade my new old stock Huawei P9 EVA-L09, its driving me absolutely crazy. When I bought it, like an idiot, I didn't check the Android Version, which I discovered was 6. So, I did oodles of research, gathered the right tools, downloaded the suggested updates and started.
I successfully upgraded to the latest android 6 (L09C432B210), but I tried many versions of Android 7, but to no avail. I eventually found a version of Android 7 called 'L09C432B322' that worked, but when I checked it says 'NRD90M test-keys', which is EMUI 5, Android 7; it is a fully functioning version of Android 7 but it is a pre-release version I believe, and neither the 'Files' option nor the 'Update' option are available on it, which is a pain. I have now tried a total of 23 different update versions, but no success, and with exactly the same issue with the update process, saying that it cannot update using that version (not precise wording!).
A couple of days ago I accidentally ended up on the phone update screen, the one with the big circle, while I was trying to get in to TWRP (fat fingers...). It sat there for an age doing absolutely nothing (aside from the circle spinning), not even failing, and I didnt even have an update file in 'dload' on my SD Card (not that I'm aware of), so I pressed the power button and shut it off. Now when I try to update, using either update.app via manual update or update.zip via HWOYA7, any update at all tbh, even old ones that I know failed but at least the update file was seen by the phone & process, it tells me the install failed and 'the update package does not exist'. I thought it may be a file extension association issue in Windows 10 (not sure how, just clutching at straws), so I reset the associations to Windows default, but that did not work. At around about the same time of the update issue starting, I couldn't say for sure when as I wasn't paying enough attention, I started using the HWOTA7 tool, which too gave the same result of 'the update package does not exist'.
Did HWOTA7 cause this? Did I cause this inadvertantly? Has a broken update.app caused this? I simply do not know and am hoping one of you fine people may be able to help me. Is the process looking in a different place to where either HWOTA7 puts the file (not changed from default) or where I put the file (SD Card 'dload')?
The reason I'm trying to update is because Android 7 is no longer supported by Google and one by one apps are disappearing from Google Play, so I'd like to update to Android 8 (Oreo). There lays another fine issue as I cannot find a version of it anywhere, not since Huawei removed the updates from its site a couple of years back. Not that any update will work of course...
I've never known a phone to be so difficult to get the correct software for and to ultimately upgrade. I even managed to update an LG G5 around 2 years ago when there were no official updates, but this Huawei P9 is just silly...
I think the update process should be this, update to the latest possible Android 6 then 7 for the P9, rebrand to the AL10 and, update to the chinese Oreo and then overlay the Kirin fix (I think); is that correct?
Thanks folks.
Paul.
Hey @vorlockfoss can you send me the B322 that you have found in order to update from B210 Marshmallow to Nougat?
Huawei's firmware servers were taken down only last quarter of 2020 so october/november/december 2020 around those months.
Hi W00fer,
How are you?
B322 is the version I downgraded from, back to C900B300. If you have B210 then you'll need B386;
HWOTA.zip | by Tecalote for P9
there are instructions in the folder. It includes the full firmware for EVA-L09 C432 B386 - for update from Android 6 to Android 7. For example from b182 or b210 to b386.
androidfilehost.com
I've responded more completely to your other message, so if you need further advice it may be better to reply there and I'll do what I can to help. I will update this thread after we've finished, just to keep it tidy.
Thanks,
Paul.