Database Users

OTA Update Fails

Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.

zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA

Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...

seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?

Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?

Me too. Update failed to install. Not sure why. I have also tried unrooting.

FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?

ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..

Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.

I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.

gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?

OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are

the log is \cache\recovery\last-log

Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time

I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **

I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!

SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.

No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger

Acer Recovery?
Did Acer Recovery come with the tablet?

I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.

Update this AM in US, but...

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.

[Q] N7 4.4 update issues?

Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.

Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart

StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.

Yeah I have the latest OTA also, but I am still having the same issue!!

StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.

Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?

manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.

JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days

manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:

Update from RU1.1.112 to RU1.1.124 issue

USA user of Russian version yotaphone 2. Got notified three days ago of the 1.1.124 update but every time I tried the phone would reboot, fail to update, reboot back to android and re-download the update to try again. I made a video of what it did. After two days of trying and an unanswered tweet and support email later it magically corrected itself.
https://youtu.be/kG4tyuoOq0M
I did try copying the update from cache and sideloading. I'm rooted but with stock recovery. Recovery at least gave me a better understanding of what could have happened. Seems there was a problem with the zip. Apparently there was a problem with ALL of them since I re-downloaded it about 8 times before it worked!
I post this here as a reference.
Sent from my YD201 using Tapatalk

UK user of the same. Tried the OTA but was still on TWRP, didn't work. Then flashed stock recovery. Now it downloads, and that's kind of it: I press 'restart & install', it count down to restart then just switches to prior screen saying "your system is up to date". Going to try pulling it from the cache and adb sideload weh I get a chance.

How'd the sideloading go?
Sent from my YD201 using Tapatalk

radbme said:
How'd the sideloading go?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Any decent new features / battery improvements?

Just updating to say have got a new phone. Loved the Yota for the first year and it's use when outside is outstanding but have spent far too long trying to update and fix things, it doesn't really last more than a month without getting intolerably slow so I've upgraded. Might get around to sorting the Yota out but probably more likely to just reset it and save it for sunny days reading in the park or summit.

Completely stock ONN 8 won't download an OTA.

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