Hot answers tagged ota-update
8
You almost always lose root when installing an OTA update. I would keep an eye on RootzWiki or DroidForums for someone to confirm that it can be rooted or someone to release a rooted update.
7
There are many variations of the Galaxy Nexus. Most likely, your phone is yakjuxw, which gets the updates from Samsung. The other phone is either yakju or takju, which use Google's own updates, which are released quicker.
The versions are interchangeable, if you don't account for international customizations or possible carrier modifications. For example, ...
5
I waited very impatiently for the JellyBean update for few days last week and finally did this to get JB on my Galaxy Nexus.
Manually trigger the update by clearing the data in Google Services
Framework and then check for System Update in Settings.
You might have to do this multiple times though. I had to do it 5 times to get the update. You might be ...
5
I had the same problem: I bought my phone from Amazon.com and got stuck on 4.0.2 with no OTA upgrades. When I looked into it, it turned out that I was running a firmware (yakjujp) that was set to get updates from Samsung, as opposed to getting them directly from Google.
First you need to determine if your device is receiving updates directly from Google, ...
5
Yes, what Cheuer said.
Installing an OTA while you're running a customized ROM in any way (even just rooted) pretty much always screws up root, sometimes even having a high risk of bricking your phone. NEVER install an OTA update while running customized software. If you ever want to go back to stock software, you need to go find the thread for your ...
5
If you are installing a custom ROM that is not a "carrier leak" then you probably will no longer receive OTA notifications/updates.
In the custom ROMs they remove the OTA settings that the carriers use. I don't know exactly what is changed/removed, but I can't even tell you the last time I have had an OTA notification.
But if you use tools like ...
4
First of all, since you've modified the system, the OTA update could very well fail partway through -- most of those are distributed as patches against the existing binaries.
The easy way to update is to find a pre-rooted stock ROM, like this one. You may need to update your radio first though, information and download links are available here. I think ...
4
Ok, here is how I solved the problem:
I followed the first part of the directions here: http://oldwiki.cyanogenmod.org/wiki/Motorola_Droid_2_Global:_Full_Update_Guide to wipe the flash and install older version of the Motorola software. (specifically, section 2.1.1) Then I upgraded to the version that I was running before the update started attempting to ...
4
I would suggest flashing the stock ICS (or Gingerbread, if you prefer) ROM via Odin. Full instructions here.
Get the official image from http://www.sammobile.com/firmware/ (search for "N7000" and select the download for the appropriate region.)
Download and install the USB drivers (for 32 bit or 64 bit Windows)
Download the Odin tool.
Extract the contents ...
4
I have the same problem for about half of a year. I've tried entering "checkin" secret code in phone Dialer many times, many weeks in a row, tried to clear data of Google service framework - no luck.
But yesterday I've finally get updated to Android OS 4.1.1! Here is how I did this:
open phone Dialer, enter *#*#2432546#*#* (numbers is representing word ...
4
ROM Updates from vendors/manufacturers/carriers usually evaluate checksums of at least the system partition -- which fails in case of applied modifications, such as required by rooting (rooting needs to place at least the superuser apk on the system partition, and other root-apps may then add to it). I'm not sure how this is handĺed by HTC for devices ...
4
Ok, found the answer here
When you start the update process it loads that screen with the android character and the yellow progress bar, as soon as that screen shows up press both vol up and vol down at the same time and it will switch to verbose mode where it will show each step of the install process. When it fails it will typically display a directory ...
3
Hurrey!
After quite a bit of research I am now able to answer my own question. I was able to clean install Jelly Bean (in opposite to the usual method of upgrading) using official images posted by Google. This obviously solved the issue.
Here are my instructions how to do this.
3
If your handset is Google Nexus, then yes, Google pushes out the OTA updates.
The rest is down to the carriers, depending on who you are with, what handset you have.
Edit: Added more thought for clarity.
Some may not roll out the OTA updates, its all dependent on the market, region. I am with O2, and never get any OTA updates what-so-ever. Some ...
3
I had the same problem with my wifes phone(lg g2x p999) Unfortunately your going to have to master reset....if it doesnt work from the settings, then reset manually(hold power button and volume down till you see the andriod guy then let go) after that your phone will be reset and the downloading issue will stop. Read through these steps prior to resetting to ...
3
Looks like you aren't the only one with this problem. A simple reboot seems to be working for most people, with some having to do a factory reset. If you have to do that, don't forget to use an app such as Titanium Backup to back up your apps first.
3
It appears that the Ice Cream Sandwich update for the Galaxy S2 on AT&T was never pushed over the air, but only via Samsung Kies.
In order to install the update you'll need to install and use Kies. If you do, I strongly recommend creating a system restore point (Windows) before installing it.
3
Two pieces of ground I want to cover here:
/cache is typically a separate partition on your device, which wouldn't be mountable by a PC via USB, which is why that isn't working. The USB connection generally accesses a directory named "sdcard" (or similar) which is used as an external storage device, although this storage area doesn't have to be physically ...
3
The devices which were bought from Google Play is takju. and From Samsung is Yakju.
I think your phone is Yakju(Google Play didn't sell Devices in india).
Takju gets All Upadte Directly from Google.
If you want to get all update from Google at the time of release you have to convert to Takju.
How Can you do that
Please follow below to convert from yakju ...
3
The update is just a bug fix update, no new features. The lock screen bug that you mentioned allowed bypassing the lock screen for a short amount of time, details can be found for example on TheVerge or AndroidCentral.
2
That's very odd. Normally there should be no auto-update of the device software, and other updates will require a reboot. Try the following:
Hold both volume buttons and the power button
Wait until the phone reboots, keep holding
Release the power button about 1 second after the white text with your phone model appears onscreen, keeping holding the ...
2
If this is a standard OTA update then you shouldn't lose anything at all, and the update should take less than half an hour, just make sure that your battery is fully charged before you start. All your apps, data and configuration should stay. The only exception to this is where things have changed between Eclair and Froyo, so some of your apps may not be ...
2
Two possible reasons:
Your carrier hasn't released the update to their customers yet. Check their support website or call their support to ask.
If you have ever rooted your phone and removed and of the systems applications, which includes bloatware apps like Facebook that come preinstalled, you cannot get OTA updates as your phone's system won't match ...
2
With the Galaxy Nexus it's sometimes tricky to tell who is responsible for the updates. There are (at least) four different variants of the GSM/HSPA device and one CDMA device.
GSM/HSPA:
yakju
takju
yakjuxw
yakjukr
CDMA:
mysid
There used to be an app in the Play Store which could tell if your updates come from Samsung or Google, but it's been ...
2
The manufacturer is responsible for the Android updates (not only if it's an OTA Update).
But some carrier branded phones receive a different firmware as the unbranded ones because of custom carrier modifications, like removing the WiFi tether feature. Therefore a delay for an update can also be caused by the carrier. Usually you will see an update first ...
2
Having "root" just means you have a working su binary installed (the "su" application is generally just a management front-end for the linux-level binary installed in /system/bin or /system/xbin). So, something has gone wrong with the binary, or the way its installed, or its permissions, or its location, or ...
I suspect the apps that still work must have ...
2
You can try forcing your device to ask for a free download slot:
Settings > Apps > All
Find Google Service Framework in the list, tap on it
First tap Clear Data, then Force Stop
After this procedure the last checked date under Settings > About Phone > System Update should have been reset to 1970 or so. Tap the Check now button there and see if the update ...
2
There's an app for this. You can use it to install Flash Player on a Jelly Bean device.
You can also try installing Flash Player and then upgrading the device to Jelly Bean.
2
You are looking for FOTAKill.apk, it kills the Firmware Over The Air (FOTA).
"Prevents GoogleServicesFramework from downloading OTA updates"
It's a fairly standard apk used and provided with some gapps packages (google apps package, when you install a custom ROM you don't get the google apps, need to install a gapps package)..
It works for both stock and ...
2
Don't use full image at recovery! It contains recovery too (CM can repair itself, but reflash of bootloader is not needed).
Use fastboot and flash partitions: system, data
You will loose all you data on tablet, but it needed because of different filesystem structure. Without reflash data you will get bootloop.
Only top voted, non community-wiki answers of a minimum length are eligible
