I'm in Canada, on Bell. using the baseband version i9000UGJL2. Its not rooted or anything.
it started yesterday, but I can't connect to twitter, through apps, or even through the web browser. It will work if I have the phone on Wifi, but it won't work on 3G/HSPA. All other apps and websites work fine.
There's appearantly a new firmware out, but Kies won't let me update to it. I tried using the registry editor to force the update, but when the process starts, it stops and says its not available for my firmware version.
I had to use Kies (older version back around the new year) & the 1.7 reg editor to force update to froyo. Is there anything else I can do with what I've got? Or do I need to look into rooting it? I'm kind of new to all this, so any help would be appreciated. TIA
What new firmware ??
Most likely a Twitter/ your Twitter account /settings problem as its both an app and web problem .
Rooting will not help that's only gaining administrator rights over your phone .
jje
Hey guys
I'm using a Verizon Galaxy Tab but I do not have it connected to Verizon's network as I am using it WiFi only. I've gotten a few notifications saying there is an update available but every time I click "reboot and start download" my device simply reboots and does not begin the download. I'm assuming this is because I am using my Galaxy Tab wifi only. I've tried Kies and my device doesn't want to connect via Kies for some reason. I'm hoping there is a way I can simply download the 2.3 file and update within the device itself. My device is not rooted. Any help would be greatly appreciated.
Im using a verizon wireless Tab on wifi also with no plan or account with verizon. The update will still get pusked to the device. I did not get the notification, but instead I went to settings/about device/system updates.
Thats where I found out about the update. I don't remember if I had to click anything to start the download but give that a try.
Thanks for the response. I tried this but it says my device is up to date but I'm still on 2.2. It's strange because 3 times I've gotten a notification that said an update was available but each time I try to update the device reboots but doesn't install the update.
Hi all , 1st post here so hi from Scotland.
As t' title says I'm having Hassle's updating my GT-N7000 from 4.0.3 OTA vie settings/about phone/software update/update. It downloads fine, reboots and runs the extraction/update however when it gets to the home screen I'm told that the update has failed and to connect the phone to a PC via Kies Air. Only problem is I don't have a PC but i do have a nexus 7 13 which says is incompatible with kies according to Google play.
So I'm here begging favours people, anyone got a suggestion or workaround thingy? And thanks for reading.
Is the device rooted?
No, there's a couple of launchers installed but it's not rooted.
I was wondering if I downloaded it and then booted to the boot-menu if I could run it from there, but then would that make a difference?
You can make a backup of your files & settings and do a factory reset. Maybe after that the ota update works. Give it a try, if not you need a PC and flash latest Stock Rom...
Thanks User_99,I'll give that a try. :good:
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
Hey guys. I found a new firmware that is approved for my device (not ROOTED) . It doesn't show up in my system update when I checked. So I tried the built in methods in the firmware finder app and it didn't show the latest update in the System Update app.
Previously, I have used the Proxy and DNS methods to install updates via firmware finder app, but now it seems those methods don't work as well. Are there any other ways to get the update?
The proxy method from the app still works fine for me. Just did an update two days ago to the August Google security patch. Just make sure that when using the proxy method that:
a. change your wifi connection to "local host" , port "8080"
b. go to system update in settings and begin the update
c. when the update is at 5-10% pause the update
d. go back to wifi settings and return your settings to normal by removing "local host" and "8080"
e. return back to system update and continue the update.
brookie229 said:
The proxy method from the app still works fine for me. Just did an update two days ago to the August Google security patch. Just make sure that when using the proxy method that:
a. change your wifi connection to "local host" , port "8080"
b. go to system update in settings and begin the update
c. when the update is at 5-10% pause the update
d. go back to wifi settings and return your settings to normal by removing "local host" and "8080"
e. return back to system update and continue the update.
Click to expand...
Click to collapse
I tried this. Doesn't work for me though