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


12

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


10

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


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


6

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


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.


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

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


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

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


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


4

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


4

Nope, there will be no official support for Android 4.4 on the Galaxy Nexus. However, you will almost certainly be able to flash custom ROMs that are based on it. There's some supposition and explanation going on on Android Police. They make a few good points: The Galaxy Nexus is old and well outside normal support windows. The CPU Manufacturer doesn't ...


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

I had the same problem with my wife's phone (LG G2x P999). Unfortunately you're going to have to master reset.... If it doesn't work from the settings, then reset manually (hold power button and volume down till you see the Android guy then let go) after that your phone will be reset and the downloading issue will stop. Read through these steps prior 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 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.


3

If your device is rooted, and you have a custom recovery installed: Wipe the dalvik cache. Next boot will take a little longer (as the Dalvik cache has to be rebuilt), but the problem should be gone. If the above is not an option, you could try to backup the affecgted apps and their data using e.g. Helium Backup, then uninstall the apps, and restore them ...


3

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


3

If you root the device on the stock ROM, it will still offer to do OTA updates, but they won't work. OTA updates only apply to a completely clean system image that hasn't been rooted. To apply an upgrade to your rooted device, you have to download the ROM image from the official Google site and follow the instructions there to flash it.


3

Since you bought your phone from Kuwait, the phone has the Kuwait Galaxy Note 2 Rom, and still now the 4.3 update has not been pushed out in Kuwait or the middle east region for both the note 2 and s3. But for the Indian Rom 4.3 has already been pushed out for both the phones. My brother had the same problem with his s3 and since I have some knowledge in ...



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