I just received an update from Acer. Version 1.141.xxx where xxx are numbers that I can't remember. I got this by manual update. I think this is an update version for the U.S
I got the Update here in Germany
The version is 1.141.01, also by manual updating ...
Got it too. But mine failed. Said update was invalid. I'm rooted but only froze certain apps. Unfroze them before update. Guess I should have rebooted. Are you guys rooted? Did they include a change log?
*** Rebooted and manually updated. Updated successfully. Now to find out what was changed...added
Duke
Sent from my A500 using XDA Premium App
Yep mine fail the first time. Tried to download and install the second time and it was successful
sweet, wifi stable, GPS, I got a location fix for the first time. I am happy
I reverted all renamed apks (like Email.apk and Phone.apk), unfroze disabled apks, I even unrooted my Iconia, rebooted it prior to updating, but the update still fails.
I've deleted some apks a while ago, but restored those files from a backup, but only the apk-files, no odex-files, assuming that those will get generated.
I will try the update later at home, where I have my power supply. Maybe it fails because of running from battery.
Update requires the unit to be plugged in and battery level at least 30%
wow this is my 3rd time it failed twice already...
I'm rooted but don't know what's really causing the fail.
It reboots the bar goes half way then stops?
Mine is a stock US 16GB WiFi model. The update failed the first time but worked when I manually asked it to update. It asked that I please keep it connected to the charger during update but I had 70% battery so I left it unplugged and it worked fine. I am now at the firmware version mentioned above.
When mine failed it happened immediately after downloading the update. It never rebooted into recovery to perform the flash. If its failing during the flashing step, my guess is that you've missed something when reverting everything. You'll probably have to dd a working image before proceeding or find out what app is screwed up / mismatched.
Mine also failed initially until it was plugged in. Make sure you're plugged in before applying the update.
oh my gosh while Im reading this I said ****!n yeeeah updates!!!
and turn on screen of my iconia and I see this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the 3rd failed attempt to update I remembered I had tried that netflix hack where you change your build.prop file soon as I chnged it back update success!!! So if you tried that netflix hack revert your file back to stock then try again.
My unit was running on battery at about 70%. Updated fine after I unfroze apps and rebooted.
Duke
Sent from my A500 using XDA Premium App
mmmm when update is installing, progress bar desapear and appears a exclamation simbol inside a triangle and when a500 start update fail.
is there a way to know which files are causing troubles with update? any log or something, I already unfreeze all apps with titanium
Alejandrissimo said:
mmmm when update is installing, progress bar desapear and appears a exclamation simbol inside a triangle and when a500 start update fail.
is there a way to know which files are causing troubles with update? any log or something, I already unfreeze all apps with titanium
Click to expand...
Click to collapse
same here - maybe because i didn´t connect the charger because it´s at home
cptkirc said:
same here - maybe because i didn´t connect the charger because it´s at home
Click to expand...
Click to collapse
I have 100% battery and connected charger
what the hell
its just about Link to adobe flash and link to facebook
****!in acer bullsh!t hahahahaha
If your update fails, just browse to /cache/recovery/last_log and view as text and there is all about sucess of failed update
babyboy8100 said:
wow this is my 3rd time it failed twice already...
I'm rooted but don't know what's really causing the fail.
It reboots the bar goes half way then stops?
Click to expand...
Click to collapse
According to my recovery log, it says build.prop doesn't have the expected SHA1 checksums. Not surewhat to do about this one.
Alejandrissimo said:
what the hell
its just about Link to adobe flash and link to facebook
****!in acer bullsh!t hahahahaha
If your update fails, just browse to /cache/recovery/last_log and view as text and there is all about sucess of failed update
Click to expand...
Click to collapse
Ok progress bar still there after restore Linktoadobeflash and linktofacebook apks and odexes
I hope update do not fail again.
Update: Update sucess (or something like this but in spanish )
I have received the update to 1.141 on th emea cus7 version.
When checking /cache/recovery/last_log it tell me that "/system/app/AcerDLNA.apk" does not have the expected check sums...
Can anyone provide me with a download of this file from the EMEA Cus7 version?!
Related
OTA update notice this morning even though it's a JF signed build. It stated something about "security".
I Pulled the battery and booted with home+power and reapplied JF rom from SD.
The battery removal may have been adequate, But reapplying the update.zip may also have been what helped me to avoid the update for now.
I'm disabling my APNs, etc. until somebody finds a way to keep them from updating these phones.
I got the same message, I thought i had missed something since i havent been on the forums in a while.
any help would be nice on this issue
Mine is also downloading the update,and i'm on Cyanogen's rom!WTF?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also,the updates from Google not tmo.
What version of the respective ROMs are you guys running?
Cyan 3.6.7-2 here and I haven't seen this message..
Nedlinin said:
What version of the respective ROMs are you guys running?
Cyan 3.6.7-2 here and I haven't seen this message..
Click to expand...
Click to collapse
Running the same here, no update yet but I've disabled apn's just to be safe until I find out what exactly the update does.
I'm running Cyan's 3.6.7.2
If i go to settings>about phone>system updates it tells me download complete requires restart.i restarted the phone but nothing happens,it starts to download the update again.
Quick question just recently rooted my G1..anybody having any problems with this? i mean can't we always just downgrade and rehack if worst comes to worst?
im using the JF US cupcake
running cyonogen experimental build and have yet to see an update
See http://forum.xda-developers.com/showthread.php?t=538059
http://jf.andblogs.net/ look here for your answer as to why your getting the updates
Haven't seen this on Cyanogen 3.6.7.2
Shane2 said:
Haven't seen this on Cyanogen 3.6.7.2
Click to expand...
Click to collapse
Just checked for kicks and it's there, I'm running Cyanogen 3.6.7.2
stop worrying, even if you download it, you wont be able to install it.
bilydkid1970 said:
OTA update notice this morning even though it's a JF signed build. It stated something about "security".
I Pulled the battery and booted with home+power and reapplied JF rom from SD.
The battery removal may have been adequate, But reapplying the update.zip may also have been what helped me to avoid the update for now.
I'm disabling my APNs, etc. until somebody finds a way to keep them from updating these phones.
Click to expand...
Click to collapse
I haven't touched APN's.
Turn off Data Roaming by going to Settings > Wireless Controls > Mobile networks
This worked wonders for me. I never got a notification about OTA updates again... more importantly, my phone doesn't shut off randomly anymore.
I'm running JF1.51 but that shouldn't matter...
remiks3 said:
I haven't touched APN's.
Turn off Data Roaming by going to Settings > Wireless Controls > Mobile networks
This worked wonders for me. I never got a notification about OTA updates again... more importantly, my phone doesn't shut off randomly anymore.
I'm running JF1.51 but that shouldn't matter...
Click to expand...
Click to collapse
dude when u install a build thats the first thing u should check unless u want a surprise 500 dollar or more bill
I've had my phone since end of November so its one of the original rev.
Just a few minutes ago I rebooted my phone to recovery and this is what happened.
- Rebooted to Recovery (TWRP)
- Screen turned White
- Didn't do anything and went to take a picture of it.
- Took a Picture (view below)
- Then it loaded TWRP but screen is still flickering
- Didn't touch anything and it went to the bootloader menu and screen was still flickering.
What I mean about flickering, the screen was still viewable just the brightness was going higher and lower.
- Rebooted back to System (still flickering), tried to record it but couldnt really since the quality of the cam couldn't see what was going on.
- Rebooted back to TWRP, loaded it fine but still flickering.
- Rebooted back to System and it went away.
- Rebooted back to TWRP and it looks fine.
Modem: .83
OS: 4.3
ROM: Paranoid Android 4.3 August 16
Kernel: hells-Core b33-ANY
Now someone might say oh its the kernel, probably kernel or ROM. But this happened in both the bootloader menu and TWRP and during that time ROM and kernel wouldn't be running.
Anyone has had this happen, please share your experience
Wanted to know if this is a known thing or my phone is starting to die?
Only dropped once like 6 months back and thats w/ a hard case on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).
sandy-achar said:
Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).
Click to expand...
Click to collapse
Ah alright thanks, good to know I'm not the only one or at least its known.
I practically flash my phone weekly/daily and never had that happen to me before so when I did it today I was like wth lol. Now with my experiences with computers when it something flickers like that or graphic errors we think drivers and if its not loaded up we think its memory dying so I was already trying to diagnose it lol..
But if its a known issue guess I cant do anything about it, at least its back in working condition :good:
The same thing has happened to me, but when I am running Google Maps. The first time it happened the screen became unresponsive and I went to reboot and had the same flashing screen you are describing. I started freaking out and went to reboot again and it was persistent in the boot screen each time. After about 5 minutes it stopped but I still have issues with my phone freezing with Maps and now when I look at flash videos on the stock Browser (I don't use Chrome).
I had a similar issue with my Macbook Pro when I accidentally block the exhaust but my phone is set to very lore frequency's with SetCPU.
I am using AOKP Milestone 2 and Ziddy's kernel for OTG support.
Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.
i
Serotheo said:
Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
I have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.
Click to expand...
Click to collapse
did you Wipe completely and then install fresh rom?
1. wipe completely through recovery (cache/dalvik/data)
2. install Fresh (latest nightlies) firmware
> if problem remains after few hours (without any extra customization) it might be the hardware problem... so take it to a services.
:good:
I have done those entirely.
Hello, I have an old NOTE 4, ive had it since release date but ive started to get issues, its only happened in the past month, ill explain every single thing that is happening below.
1. When switching from apps sometimes it will take so long to open the app and during this time i literally cannot do anything, cannot open the app drawer to force close apps, cannot slide from the top to see the notification bar, after a 30seconds it will lock the phone screen (The time i have the timeout on i suppose) and then i cannot even open the lock screen nothing literally works, maybe after a minute or two it will finally let me. Sometimes a battery pull is needed.
2. When typing it will lag and do the same thing above with the freezing, and even during these processes once the screen goes black (sometimes i can still see the notification bar) the phone will completely restart itself on its own.
3. Just other general slow downs.
Here are the steps I have done to try and solve it (still no luck)
1. Wipe Cache and Dalvik Cache through TWRP.
2. Uninstalled apps and cleared out files
3. Installed an antivirus software and run tests.
4. Formatted SD Card (Removed it as well)
5. Completely formatted the whole phone (Every single bit of data (selected all options in TWRP except SD Card) so it says no OS has been installed.
6. Installed the latest stock firmware through samsung kies.
All of the issues are still happening, whether i root it or not, it will do the same. Im out of ideas and have no idea what to do. Its becoming so annoying having to constantly pull out the battery and what not.
Hmm I don't know what to say as you have already done a complete wipe! But I don't understand how you flashed the firmware through Kies though! Doesn't than need an already working phone with a ROM already installed? Don't know, have not used it for long time.
Just try to flash the stock firmware via Odin once, see if that makes any difference, after a complete wipe of course. And please don't use any anti virus, that's not needed at all.
Buy a new phone! ?
macmobile said:
Buy a new phone! ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which Apps are installed on your phone? In which Apps is this Problem happening? You said: "Switching between two Apps"
ithehappy said:
Hmm I don't know what to say as you have already done a complete wipe! But I don't understand how you flashed the firmware through Kies though! Doesn't than need an already working phone with a ROM already installed? Don't know, have not used it for long time.
Just try to flash the stock firmware via Odin once, see if that makes any difference, after a complete wipe of course. And please don't use any anti virus, that's not needed at all.
Click to expand...
Click to collapse
you click tools and do a firmware installation and upgrade, but I'm I'm out of ideas
macmobile said:
Buy a new phone!
Click to expand...
Click to collapse
Yep its seeming like its going that way
Install cm 12.1 or 13. I have the same problems with touchwiz firmware and roms.
Akuma360 said:
Install cm 12.1 or 13. I have the same problems with touchwiz firmware and roms.
Click to expand...
Click to collapse
Well it never used to do this so I can't see it being touchwiz, I just think the phone is nackered
Sounds like something is seriously off with your phone and that it needs to be repaired.
MichaelK18 said:
Hello, I have an old NOTE 4, ive had it since release date but ive started to get issues, its only happened in the past month, ill explain every single thing that is happening below.
1. When switching from apps sometimes it will take so long to open the app and during this time i literally cannot do anything, cannot open the app drawer to force close apps, cannot slide from the top to see the notification bar, after a 30seconds it will lock the phone screen (The time i have the timeout on i suppose) and then i cannot even open the lock screen nothing literally works, maybe after a minute or two it will finally let me. Sometimes a battery pull is needed.
2. When typing it will lag and do the same thing above with the freezing, and even during these processes once the screen goes black (sometimes i can still see the notification bar) the phone will completely restart itself on its own.
3. Just other general slow downs.
Here are the steps I have done to try and solve it (still no luck)
1. Wipe Cache and Dalvik Cache through TWRP.
2. Uninstalled apps and cleared out files
3. Installed an antivirus software and run tests.
4. Formatted SD Card (Removed it as well)
5. Completely formatted the whole phone (Every single bit of data (selected all options in TWRP except SD Card) so it says no OS has been installed.
6. Installed the latest stock firmware through samsung kies.
All of the issues are still happening, whether i root it or not, it will do the same. Im out of ideas and have no idea what to do. Its becoming so annoying having to constantly pull out the battery and what not.
Click to expand...
Click to collapse
Did your baseband somehow change. That will cause super serious lag issues and it will not get any better until you reflash modem. Also maybe try a different kernel
jlbuck6212 said:
Did your baseband somehow change. That will cause super serious lag issues and it will not get any better until you reflash modem. Also maybe try a different kernel
Click to expand...
Click to collapse
How do I find out? And how Can I try a different kernel, I'm not too into the scene to have much knowledge
Good afternoon
I just got a new update system for my watch but when is verifying the download always came with the same error:
"Can't install system update try again?"
And i´m tired to say yes but always return the same error.
I have restore the watch but still giving the same error
Can anybody help me please
Me too & same problem!
Same issue here. New System Update for my Ticwatch Pro. Can't install. Gets to "Verifying" and then "Couldn't Install Update". Error Message won't go away...
Same here! Very annoying.
I confirm, the same for me!
Ditto, just started today, I've got about a gig of spare space on the watch. Looking around it's a problem that has occurred for various watches in the past, but there never seems to have been any accepted resolution for any of them other than one for a Wear 1.5 watch which involved reflashing the watch with downloaded firmware. I'm not doing that until a bit more desperation sets in. The notification can be ignored by long-pressing it after all, and the watch still otherwise works so at the moment it's just an annoyance.
Ditto
I'm hoping that they'll make a fix and replace this update that is not working
Same here!
Same here (and factory reset doesn't fix it either)!
To me its almost as if it can't finish or start downloading the package and thus it keeps failing the verification stage. I wonder if it is just a server issue. Either overloaded, the bits aren't ready yet, or another mistake.
Someone has allegedly called Mobvoi support and reported there findings over on Reddit (TicwatchOfficial).
According to the user, Mobvoi missed a deadline to have 2.3 ready for release by Google from their server. Google pushed it anyway, however there is no update file on the server to push hence why all Ticwatch Pro's are reporting the update failed.
Mobvoi's comeback was it should be sorted in the next week or two.
ReDaved said:
Ditto
I'm hoping that they'll make a fix and replace this update that is not working
Click to expand...
Click to collapse
There's a Reddit thread where a user has contacted Mobvoi and been told that this will be resolved within the next week or two.
https://www.reddit.com/r/TicwatchOfficial/comments/aldx8r/ticwatch_pro_cant_install_system_update/
This message was posted by cathal S on Wear Os help by google
Hope this can solved your doubts
And thanks to This user
I found a solution that worked for me
etrobear said:
Good afternoon
I just got a new update system for my watch but when is verifying the download always came with the same error:
"Can't install system update try again?"
And i´m tired to say yes but always return the same error.
I have restore the watch but still giving the same error
Can anybody help me please
Click to expand...
Click to collapse
I had the same issue, I Uninstalled wear os on the watch and reinstalled it now I'm on 2.3, I was on 2.2 before. Update notification is gone and I checked for updates and there aren't any now!
ironsidedonald said:
I had the same issue, I Uninstalled wear os on the watch and reinstalled it now I'm on 2.3, I was on 2.2 before. Update notification is gone and I checked for updates and there aren't any now!
Click to expand...
Click to collapse
I was on the same page
I uninstalled the update, and reinstalled
The warning message didn't disapperead immediately but after few hours
it sorted itself after a couple of hours
Finally it seems to updated itself with no interaction from me. I got the error in the morning and now it's gone and the system says 2.3. I did nothing cause I had no time to fix this mess.
tvladan said:
Finally it seems to updated itself with no interaction from me. I got the error in the morning and now it's gone and the system says 2.3. I did nothing cause I had no time to fix this mess.
Click to expand...
Click to collapse
Like me ... but I was 2.3 updated before too ... when the warning message was present
Unbelievable !
Anyway ... well done
I don't want to speak to soon but it seems that the infamous lag for incoming call notifications is gone ... Finally my watch shows incoming call notifications at the same time the phone rings, not after 5 to 10 seconds. Hope this won't brake again.
tvladan said:
I don't want to speak to soon but it seems that the infamous lag for incoming call notifications is gone ... Finally my watch shows incoming call notifications at the same time the phone rings, not after 5 to 10 seconds. Hope this won't brake again.
Click to expand...
Click to collapse
Good
It was not a mine issue but proud for you
Inviato dal mio Mi A1 utilizzando Tapatalk
After a factory reset and a full charge overnight, my phone came back to the July 2018 Update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like the Wear OS 2.3 (January 2019 Update) is the trouble causer.
Just so people understand.. There are 2 separate updates which have been rolling out. "WearOS 2.3" and "System Version: H" otherwise known as Update H.
You update to WearOS 2.3 through the Google Play Store.
You get the "System Version: H" update through the System Update menu.
The "Downloading Update" message we all got was due to something on Mobvoi's side, either because they screwed up or because of the WearOS 2.3 update. There was no update actually available, so the watch would try to download something which wasn't an update, and there was nothing to install. It looks like Mobvoi has fixed this issue, so now our watches don't erroneously think an update is available anymore.
Hopefully the "System Version: H" update will be released by the end of February, as Mobvoi has told some other people.