Tag Info

Hot answers tagged

22

The before and after screenshots of the about screen confirm that I had the exact same Android, Baseband, and Kernel versions, as well as the same Build Number Actually, they do not. The first screenshot shows a build number of JWR66V, and the second is JWR66Y. An official changelog has not been released, but T-Mobile's documentation indicates that the ...


17

It sounds like the "/system/bin/app_process" has been modified and so it doesn't match the signature required. There are 2 ways to fix this, either get a copy of the stock file from another phone/rom or flash the factory image for 4.3 Edit: After reading "update 2" it sounds like you want the factory image option detailed below. AndroidPolice has a step by ...


15

You can disable these notifications by unchecking the notifications for Google Play Services [Not Framework]. This fixed my problem on the LG G3 and I assume it will on all other devices. The best option is to click and hold the notification and then select 'App info', which will take you to desired app info for that update notification. Then uncheck the ...


13

It appears to be random chance. In this reddit thread, Google Employee Dan Merrill says of OS update rollouts and "mashing" the "check for updates button": Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure ...


12

OTA updates that come directly from Google (such as Nexus devices) are rolled out in waves. An excerpt from Dan Morill's comment states that, specifically: Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure ...


11

OTA updates don't wipe the device: all apps and data are preserved across the update. Even so, it's always a good idea to back up your data frequently. As you point out, not all apps support the in-built Google backup mechanism, so it's wise to have a full backup just in case. See our backup tag wiki and top questions to learn about what options are ...


10

FOTA - Firmware Over-the-Air This is the update sent to the OS via your service provider(for 3G/GPRS/EDGE..) or Wifi. It will download an image of the new firmware from the server and install it after you accept.


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.


8

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, ...


7

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 ...


7

Goal If you have the OTA image downloaded and, as in my case, ended up without success you should be able to adb sideload <filename> it still manually (video here). Problem/Error ... unfortunately the OTA update via adb sideload errors out with: Finding update package... Opening update package... Verifying update package... Installing update... ...


6

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, ...


6

So I tried to "Clear Data", instead of just "Clear Cache" in the Google Service Framework (and Forced Stop). I then ran the checkin again (Dial *#*#2432546#*#* in the phone app), and now I'm being shown the new Android 4.3 System Update.


6

CyanogenMod has its own OTA Updater. You will not get the official Android updates, but the CM updates.


6

Since Android 5.0, any modifications to /system will cause OTA updates to fail. Android Police noted that: ... the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Therefore you have 2 choices if you want to update your device. Remove any modifications to the system ...


5

No, you don't. The updates are received from the Servers of the Provider/Manufacturer. This adress is saved in the ROM. So you just need an internet connection via 3g or wifi.


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 ...


5

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 ...


5

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 ...


5

The devices which were bought from Google Play are takju and the ones from Samsung are akju. I think your phone is yakju (Google Play didn't sell Devices in India). Takju gets all updates directly from Google. If you want to get all updates from Google at the time of release you have to convert to takju. How Can you do that Please follow below to convert ...


5

The roll-out for all (or at least most) OTA updates is staged in case there is an issue which has not been noticed. The 4.4.2 update seems to be being rolled out quicker than the 4.4.1 update, but it won't be available to all devices at the same time. You should receive the update in a few days. This post by an android engineer explains the process a bit ...


5

I think your best bet is to unroot your device and restore it to stock. This means stock ROM, recovery and kernel, and you will be unrooted. This is often referred to as "flashing a factory image", sometimes incorrectly. But that's what we're going to do! Note: This process will wipe your phone completely. Backup your storage before you continue. I am ...


5

Another option, without wiping any data, is to when an OTA update is available, get the direct link and download the zip file to your PC, download the latest image version of your custom recovery (eg TWRP) and the latest SuperSU zip to your PC connect your device to your PC and reboot into bootloader mode then dirty flash the stock boot, recovery & ...


5

The answer is the update won't push through if you have a custom recovery like TWRP. I had to restore the stock recovery using the Nexus Root Toolkit. Then the update showed again, and it went through flawlessly. Even the re-rooting part (again using NRT) was perfect.


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

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

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

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

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible