Database Users

My tablet doesn't see the ICS OTA update

Hello,
I'm trying to check for the ICS OTA update for my Iconia A500 but i keep getting the "Your device is up to date" answer since 2 days.
My A500 was never rooted, it is running the official 3.2.1 ROM, and was only updated with all previous official OTA Acer updates. More details here below:
Model Number: A500
Android Version: 3.2.1
Kernel Version: 2.6.36.3+
Build Number: Acer_A500_7.014.14_COM_GEN1
I've also tried to uninstall and reinstall the "ICONIA TAB Update Enhancement" app from the Google Play store but it does not work either.
Any idea why my table can't see the official ICS OTA updated?
Thanks

Be patient maximum 2 more days , it will update soon.

Did you get the update app in Google play? Search Acer it should be right there. I did that last night and this morning I updated to ics
Sent from my ADR6350 using xda premium

Kinz1980 said:
Did you get the update app in Google play? Search Acer it should be right there. I did that last night and this morning I updated to ics
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Yes, as mentioned, I also tried to uninstall and re-install the Acer "ICONIA TAB Update Enhancement" application from Google Play but the OTA update is still not visible

I also do not have a System Update under the system settings option. I am rooted and did have flexreaper ics, but went back to stock 3.2.1 with root and busybox..... but no update option showing. Any way to fix this?

No Joy as well
I have not received the update as of yet. I am sure it will update. I wonder if they have delayed the update due to some of the issues I have been reading about the past day.

no ics yet?
any idea what's up with the 1/8th of us without ICS update?
In vancouver, BC, running latest upgraded iconia a500 1st gen

newdad23 said:
I also do not have a System Update under the system settings option. I am rooted and did have flexreaper ics, but went back to stock 3.2.1 with root and busybox..... but no update option showing. Any way to fix this?
Click to expand...
Click to collapse
I am having the same problem. I downgraded back to Honeycomb 3.2.1 and then unrooted using the ROM Manager app... I'm just confused and a little disappointed that this isn't working. I guess I shouldn't have jumped the gun and used the flexreaper rom early :/

i was having the same problem but it was me being lazy and don't want to wifi OTA from 3.01 to ICS. it turned out the 3.2 stock rom i have flashed always get the message of "your device is up to date". so i simply do a full restore of my original system and it OTA without problem. hope this would help out some of you stuck on the "your device is up to date". i noticed my updated stock rom is kept at GEN2 and GEN 2 is for US. so you guys could try to flash with the stock Acer_A500_7.006.01_COM_GEN2 rom and see if it would solve your problem if you never backed up your original system. Below is the link with all the stock available thanks to vache. i forgot to mention that the stock 3.2 i had flash is GEN1 that gives me the message of "device already up to date". after i wifi OTA from my original stock system 3.01 to ICS, i noticed they all have GEN2 after it.
http://forum.xda-developers.com/showthread.php?t=1113878

chris8599 said:
i was having the same problem but it was me being lazy and don't want to wifi OTA from 3.01 to ICS. it turned out the 3.2 stock rom i have flashed always get the message of "your device is up to date". so i simply do a full restore of my original system and it OTA without problem. hope this would help out some of you stuck on the "your device is up to date". i noticed my updated stock rom is kept at GEN2 and GEN 2 is for US. so you guys could try to flash with the stock Acer_A500_7.006.01_COM_GEN2 rom and see if it would solve your problem if you never backed up your original system. Below is the link with all the stock available thanks to vache. i forgot to mention that the stock 3.2 i had flash is GEN1 that gives me the message of "device already up to date". after i wifi OTA from my original stock system 3.01 to ICS, i noticed they all have GEN2 after it.
http://forum.xda-developers.com/showthread.php?t=1113878
Click to expand...
Click to collapse
OK, being fedup of waiting for the OTA update, I did the update manually myself. I've tried first to use the 3.2 GEN2 update then tried to run OTA but it did not worked ("your device is up to date"). So the only solution left was to do the update using the ICS update.zip that was available in the post URL you mentionned. And now my tablet is up and running with ICS.
Thanks a lot to all for your help and especially to chris8599

Samsung GT-P3113 OTA/Kies update

I'm curious who is getting the update to PDA:LG2 / CSC:LG2(XAR) 4.0.4 by location and what issues are you seeing after this update.
For example "New York, WiFi issues and device type".
Thanks...

I checked for the update at 17:00pdt both via Kies and OTA and there was nothing. I just started the OTA upgrade at 18:51 Kies was still looping.. I was running stock LD3 as I wanted to try the changes. I've been running CM9 since it's release up to about two days ago.
Started OTA download at 18:51 finished download 19:08
Started upgrade at 19:08 finished at 19:17
Same excellent WiFi signal ( 40MHz / n only )
Tried to Odin CWM it did not work still have standard recovery.
Southern California

bark777 said:
I checked for the update at 17:00pdt both via Kies and OTA and there was nothing. I just started the OTA upgrade at 18:51 Kies was still looping.. I was running stock LD3 as I wanted to try the changes. I've been running CM9 since it's release up to about two days ago.
Started OTA download at 18:51 finished download 19:08
Started upgrade at 19:08 finished at 19:17
Same excellent WiFi signal ( 40MHz / n only )
Tried to Odin CWM it did not work still have standard recovery.
Southern California
Click to expand...
Click to collapse
Were you rooted??

No, I flashed stock Rom prior to this upgrade. Stock Rom, kernel, recovery and no root.

Texas, unrooted stock, P3113, no issues.

My biggest problem with my tab was the touch screen. This update has solved that problem entirely, the response is very good now. Now i just need root so I can use Titanium to debloat.

settings crash
after doing ota upgrade have app that cannot load settings with out crashing aps so far CHROME. when trying to open setings tab hangs then get standard error message

Picasosz said:
after doing ota upgrade have app that cannot load settings with out crashing aps so far CHROME. when trying to open setings tab hangs then get standard error message
Click to expand...
Click to collapse
This has happened with a number of users. Believe it's a bug with chrome
Sent from my GT-P5113 using XDA Premium HD app

After doing the upgrade, the system goes through a setup wizard to choose date/time etc...
At one point it asks to enter your first and last name. Where can you edit that as I recall I made a typo.
Sent from my GT-P3113 using xda premium

I got the update yesterday, Springfield, MO. Everything seems to be more smooth. The stock web browser looks better, the keyboard looks different. I like it, I haven't had any issues with anything so far.

Alarm fails
Picasosz said:
after doing ota upgrade have app that cannot load settings with out crashing aps so far CHROME. when trying to open setings tab hangs then get standard error message
Click to expand...
Click to collapse
After update to 4.0.4, the stock alarm app fails with "unfortunately the all has stopped working." Can not restart the app.

Running stock update came up on mine yesterday I am loving the new keyboard. I haven't really noticed much else. But I'm not really looking either
Sent from my GT-P3113 using Tapatalk 2

I got the OTA notice and it downloaded the files but it would not install, i guess due to the CWM, so I turned back and flash Stock ROM but now it wont upgrade either?

Use Odin on the 4.0.4 file located here, don't forget to unzip first:
http://samsung-updates.com/device/?id=GT-P3113
Then use odin to flash this CWM ( ueblg2_espressowifi_recovery.tar.md5 ):
http://rootzwiki.com/topic/25228-ho...-step-updated-052412/page__st__50#entry821932
finally use this to root and add busybox
http://rootzwiki.com/topic/24317-cwm-root-galaxy-tab-2/

looks like they pulled the file cant download it for the p3113 anyone share it?
never mind clicked the link its working again.
but it wont unzip.......

would anyone happen to have this update on mediafire or a file hosting site?.. i'm trying to download this but it says 2 days for the D/L to finish.. and i cant get it to download on torrent either.

Will be uploading a "Mirror" Of this in a little bit to MediaFire!
«Gîzmô»

Samsung Galaxy Tab 2: P3113
Firmware Version: P3113UEBLG2
OS: Ice Cream Sandwich (ICS) v4.0.4
Release Date: 4-7-2012
Build Date: 3-7-2012
Firmware:
http://www.mediafire.com/?379jdx8wxe75o3p
http://www.mediafire.com/?zybmucd99papb0q
http://www.mediafire.com/?a9wpi9satj2f27f
http://www.mediafire.com/?wqd7j7b9c7ige7q
Kernel:
http://www.mediafire.com/?2enhmhns1ssa1ha
«Gîzmô»

I posted a de odex rooted stock Rom in the dev section. Can flash thru recovery
Sent from my ADR6425LVW using xda premium

is there a way to change the shortcuts on the home screen?

Update to 4.2.2 fails due to debuggerd

Hi,
could someone send me the /system/bin/debuggerd file from JOP40D.
It has been modified somehow and blocks my upgrade...
Thanks, Goldstein

You can extract the file using the directions here:
http://forum.xda-developers.com/showthread.php?t=1945938

Hi,
problem is, that there is no factory image for JOP40D.
In the meanwhile, I solved the problem by flashing the new 4.2.2 factory image.
But what I really like to know is, which app changed the /system/bin/debuggerd. It created a /system/bin/debuggerd.backup but this one seemed also to be corrupt (not the stock version).
I had stickmount on the device and tried to mount CIFS/SMB shares with some apps.
Maybe some knows, which app created this backup file...
Regards,
Goldstein
theninjapirate said:
You can extract the file using the directions here:
http://forum.xda-developers.com/showthread.php?t=1945938
Click to expand...
Click to collapse

You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...

Elnareen said:
You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...
Click to expand...
Click to collapse
If your on a custom recovery just use this.
http://forum.xda-developers.com/showthread.php?t=2148381
Sent from my Nexus 10 using Tapatalk HD

Elnareen said:
You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...
Click to expand...
Click to collapse
Could you please put a link to the 4.2.1 update because it is no longer available from google's site.

theninjapirate said:
But what I really like to know is, which app changed the /system/bin/debuggerd. It created a /system/bin/debuggerd.backup but this one seemed also to be corrupt (not the stock version).
Click to expand...
Click to collapse
I'm not sure I'm helping those participating in the discussion here, but for stalkers and to tie up loose threads, it was stickmount that replaced /system/bin/debuggerd, from what I've read in other discussions about why the OTA update to 4.2.2 was being blocked. I had the problem and I had installed stickmount too.

shonangreg said:
I'm not sure I'm helping those participating in the discussion here, but for stalkers and to tie up loose threads, it was stickmount that replaced /system/bin/debuggerd, from what I've read in other discussions about why the OTA update to 4.2.2 was being blocked. I had the problem and I had installed stickmount too.
Click to expand...
Click to collapse
Thanks for sharing that. I for one solved it by downloading a fresh copy of debugerd from a stock image and then applied the update.
Sent from my Nexus 7 using Tapatalk HD

Mystery system update

Hi all - I just received a notice on my Nexus 7 that there is a system update to install. I already installed 4.3 build JWR66V a couple weeks ago. Anyone know what this update is? I can't seem to find any information anywhere. My device is unlocked and rooted, running stock.

Yeah, google has released a newer version, so if you're on stock, why not update?
Sent from my Nexus 7 using Tapatalk 4

It's an update from build JWR66V to JWR66Y, still Android 4.3.
If it's an OTA update, always install it.

It fixes a couple of issues after the 4.3 update
Sent from my Nexus 7(2012) that has zero issues.

Is it possible to update via ota when the device is unlocked and rooted? I updated it but it still says JWR66V, not Y. But when I look for an update it says up to date.
Gesendet von meinem Nexus 7 mit Tapatalk 4

Got the same issue as dakoookie
Sent from my Nexus 7 using Tapatalk 4

Will this update unroot it?

Yes you'll still recieve the update it just hasnt been pushed to you yet if it says up to date. Factory images for it are already up waiting on someone to make a zip for CWM
nikola1970 said:
Will this update unroot it?
Click to expand...
Click to collapse
OTA's always remove root

Apparently not. I updated but I still have root
Sent from my Nexus 7 using Tapatalk 4

Me too, but gives error when installing =(
Rooter and bootloader unlock

Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.

nikola1970 said:
Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.
Click to expand...
Click to collapse
Then the update failed the new OTA is JWR66Y

Lol the same questions.
Every.
Single.
Time.

FYI, I lost root.

Lost root also

NeoMagus said:
OTA's always remove root
Click to expand...
Click to collapse
Guess nobody believed me :silly:
Anybody working on a zip yet for the update??
If you lost root and it put you back on stock recovery just reflash your recovery then supersu

For the folks that are having "error" during the update, restart your n7 then clear cache and data from framework services and check for updates again and it should come up. Also make sure you at least have 80% battery level:good:

It's supposed to fix the phantom screen touch problem and a few other things I'm sure someone will come up with root G.B.Y.
Sent from my Nexus 7

There's an OTA .zip for build JWR66Y here... but there appears to be a problem with symlink permisssions.
But there is also a solution here http://forum.xda-developers.com/showthread.php?t=1745781&page=53 and a modified version of the OTA that fixes the permissions. Worked for me flashing via TRWP.
Incidentally, I also lost root after upgrading... not sure why... but not a big problem, as I reflashed SuperSU v1.51 in TWRP.
-----------------------------
Not quite sure what this very minor upgrade is supposed to accomplish, given 4.3 was only rolled out 4 weeks or so, ago.... but I suspect it has a lot to do with a minor screwup on Googles part, the details of which can be found here... http://forum.xda-developers.com/showthread.php?t=2382880.
I think (and I could be wrong), build JWR66Y is {AOSP JSS15J + Gapps}... in other words, JSS15J, released as Factory Stock instead of AOSP.
And the full factory image of JWR66Y is already available on the Google Developer website here and it's immediate predecessor, JWR66V has been 'pulled' and is no longer available for download.
Anyway, take a look at the above link, and you should see what I'm getting at.
Rgrds,
Ged.

grouper zip that was linked worked great here. No issues here now

[Q] Status 7 Failure - 4.2.1 to 4.4.1 - CWM 6.0.2.3

Hey guys,
I'm no n00b to flashing, but I've been happy with my Nexus 10 being stable and set up perfectly, which is why I stayed on 4.2.1.
I've never seen error 7 before and after Googling around, I couldn't really find a solution to my problem. I'm coming from a CM build, can't recall exactly which. I was rooted, and obviously unlocked.
set_metadata_recursive: some changes failed
sdcard/0/zip
(status 7)
I'm on CWM 6.0.2.3 (about to fastboot to 6.0.4.3, just in case that's the problem)
I'm going to install Rom (cm-11-20131211), PA GAPPS, and Mod from here:
http://forum.xda-developers.com/showthread.php?t=2560613
What do I do? Did I miss a step after not flashing from an earlier JB build to now? I'm a former Google employee, but not a developer, haha. Any help would be much appreciated!
Thanks,
Travis

SPOILER ALERT. ANDROID PSA.
Hey kiddies, always update CWM first!
Updating to the latest Clockworkmod fixed this all for me. Apologies, my internet was derpy tonight and couldn't download fixes fast enough.
Thanks for understanding, hope this helps anybody in the future trying to update!