I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
just lou said:
I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
Click to expand...
Click to collapse
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
DB126 said:
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
Click to expand...
Click to collapse
Thanks. My suspicion was that it was server related.
There's like a new update ONA19TB002_20200416.
EDIT Even downloaded and installed. Kind of regret using that Mediatek tool to install 2019111 from the stock/image/ota thread as ever since then the wifi's mac address keeps changing on each boot or wifi is turned off/on.
htcplussony said:
There's like a new update ONA19TB002_20200416.
Click to expand...
Click to collapse
Interesting. Maybe someone will grab the OTA fie and upload it. Unfortunately, it probably won't do me much good, as my tablet doesn't have the November update installed.
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
no99sqrd said:
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
Click to expand...
Click to collapse
My update is still "paused". At this point I don't really care. This tablet is so slow it is virtually useless. I doubt an update is gonna make it any better anyways.
My FOTA doesn't even give any updates, just that it's "fully updated." I wonder if I got a test model, as it also came with a multitouch test, had a chinese "factory mode", and had a strange MTK debug mode when I tapped custom build mode.
My unit had an FOTA to the May 2019 but no more updates while on that firmware. The Nov FOTA from the Stock Backups thread wouldn't take and I had to flash the full stock image. It gave me the April 2020 when they released one.
New Update
I know this thread is old, but I received a new update today. It has the July security patch, and the kernel is dated 8/14/2020. It's the first update that actually installed since I got this tablet at launch last year.
Does anybody know how to overcome the problem of getting the latest OTA. I get an error after reboot and trying to flash it, here is the log:
script aborted: unable to use metadata to correct errors
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system image corrupted, attempting to recover...
script aborted: unable to use metadata to correct errors
E1004: system partition fails to recover
E:Error in /sdcard/Android/data/com.adups.fota/files/adupsfota/update.zip (Status 7)
W:failed to read uncrypt status: No such file or directory
25.10 solved the problem by reflashing the stock image from may 2019
Related
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
open /cache/recovery/last_log on your tablet use root explorer
ypu will know whats wrong
I'm in Melb too, and that particular update has failed to download about 5 times now, and when it finally downloaded, it came up with a message saying "update invalid" or something along those lines. I'm gonna wait til I get home to try and update again.
altering WPA_Supplicant file is something you would've done so your tab would connect to ad hoc networks. Must be something else.. did you alter any other files? I'm working on this same issue. frustrating as f*#%
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
acorsino said:
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
Click to expand...
Click to collapse
Same for me. Had to go back to stock recovery for the OTA update to work.
Mine failed the first time. I rebooted and it worked the second time.
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
mashilu said:
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
Click to expand...
Click to collapse
If you see the little bee fail screen, it is not the stock recovery, but still CWM.
mashilu said:
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
Click to expand...
Click to collapse
Hi .. try to do that...
the uploaded file helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (correct the link below "www")
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post link outside the forum at the moment..
just follow the steps described by Bob!
I did see that different logo, which I subsequently rebooted as I thought it's frozen again.
Interestingly, I tried to push for another system update, attempt no. 7, and now, it progresses and complete update!!! Woo hoo!
Thanks for all the help. I still don't know which one sorts what out though... Cheers!
I have attempted several times to update my new tab to touch wiz. When I update directly on the device. (go to settings about tab then check for updates), it tells me there is a 188mb update. It downloads, restarts the tab. When it trys to flash the update it gets hung up at 13% for a bit then proceeds to 28-29% then restarts failing.
On a side not I did a factory restore and diddnt even sync anything yet.
Still nothing, so I decided to try kies. It appears to be working, the tab screen says downloading, with what appears to be the proper screen. There are a few checks in the upper left corner (which I forgot, currently away from the device) it gets to the one stating something about usb and kies reports a failure, for "failure to upgrade for unknown failure"
I'm lost?
The thing isnt a week old, and has stock.
mespo365 said:
I have attempted several times to update my new tab to touch wiz. When I update directly on the device. (go to settings about tab then check for updates), it tells me there is a 188mb update. It downloads, restarts the tab. When it trys to flash the update it gets hung up at 13% for a bit then proceeds to 28-29% then restarts failing.
On a side not I did a factory restore and diddnt even sync anything yet.
Still nothing, so I decided to try kies. It appears to be working, the tab screen says downloading, with what appears to be the proper screen. There are a few checks in the upper left corner (which I forgot, currently away from the device) it gets to the one stating something about usb and kies reports a failure, for "failure to upgrade for unknown failure"
I'm lost?
The thing isnt a week old, and has stock.
Click to expand...
Click to collapse
I would take it back and have it exchanged.
roscoe_v said:
I would take it back and have it exchanged.
Click to expand...
Click to collapse
I bought it through amazon, so it would be a slight hassle. I've seen a lot of people having similar or the same problem, with this touch wiz update. I was considering just flashing it with a stock tw rom, but diddnt want to put a custom bootloader on this device just yet
Is there anything else that can be whipped? I did the factory reset onlyl
Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Godders11 said:
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Click to expand...
Click to collapse
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Many thanks, I'll give that a try.
sfhub said:
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Click to expand...
Click to collapse
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
doggie123 said:
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
Click to expand...
Click to collapse
Hmm, I wasn't expecting that to happen, just expecting some file corruption to be overwritten, but it looks like you potentially had some bad sectors in the eMMC as well that got blocked out automatically by the erase.
This reminds me of the eMMC problem we had on Samsung where they changed wipe data to do a secure erase and that triggered an eMMC bug that left people with megabytes of unusable sectors.
If I were you, I would only run my system using a JSS15Q kernel because that has the fixes for the type of issue your unit seems susceptible to.
http://forum.xda-developers.com/showthread.php?p=44954087#post44954087
Hi there! I'm running the latest (well, almost...) nightly build on my device, a Google Nexus 7 Wifi (2013) [flo]. For some reason, I haven't been able to update since the 4.4.4-20141202-flo nightly, because every single day it downloads the current update, verifies it against the MD5, then when I tell it to update it says there's a zip file signature verification error and cancels the install. I'm kind of afraid to turn that off, because last time I did that I had to do a complete factory restore on my device to get it usable again. Any ideas what's wrong?
Oh, I forgot to mention, I've also tried downloading the updates directly, still has the same problem. That's actually why I know what error message is popping up.
YmerejO42 said:
Oh, I forgot to mention, I've also tried downloading the updates directly, still has the same problem. That's actually why I know what error message is popping up.
Click to expand...
Click to collapse
That sounds like around when the DL server ran out of disk space.
Manually flash the latest from dl.omnirom.org
Entropy512 said:
That sounds like around when the DL server ran out of disk space.
Manually flash the latest from dl.omnirom.org
Click to expand...
Click to collapse
It actually started two days after that problem was sorted, and the two updates for those days worked fine. Also, as I'd said, I'd tried manually downloading the updates during this period. However, yesterday morning, starting with the update for the 7th, it started working again, so I'm once again up to date.