So, if you look at Asus's website, they have released firmware TW_V12.14.1.9 and in the changelog it mentions that "the first boot time after upgrading to Android 5.0" will take 5 mins. So I think that release is Android 5.0. It was released on April 2, 2015 so maybe we can hope to receive an OTA update for WW_V12.14.1.9 sometime within the coming week? I sure hope so!!
do not update if important sound in the headphones, disappeared after updating bass.
Before getting root solution, it's not recommended to update it yet.
OTA released since 12PM CEST, i can confirm that the version of Lollipop is the 5.0.1 WW_V12.14.1.9 which is 779MB in size.
No problem since I updated my tablet except one notification telling me that one application is requesting a newer version of Google Play Services...
Did you have root on tablet before you upgraded the new firmware and if so did you still have root afterwards?
Pirranha said:
Did you have root on tablet before you upgraded the new firmware and if so did you still have root afterwards?
Click to expand...
Click to collapse
Nop, no root...
Update breaks root. Zenroot failed.
psurut said:
Update breaks root. Zenroot failed.
Click to expand...
Click to collapse
Moreover, you can't apply OTA if you have root AND SD patch applied. Tried to install OTA, but no dice (stumped on platform.xml which was modified).
Thinktank: can you pre-root the ROM and install?
Hi, I've made an OTA update yesterday from .31 rooted version to Lollipop and I've lost root as I've expected. Beside it, tablet is unusable - still cycling messages 'Unfortunately IndexService has stopped' and 'Unfortunately ContextProvider has stopped' . I have to do super-fast double click on these messages and then I have about 0,1 seconds to click some other item before the cycling messages appear again! With this annoying double-clicking process, I've been able to reach "settings" app and make another user account - cycling messages are gone, but when I want to use Chrome, message 'Unfortunately Chrome has stopped' appears and other browser don't work too (Dolphin, Asus Browser, Chrome Beta...).
I've made the factory reset, but messages 'Unfortunately IndexService has stopped' and 'Unfortunately ContextProvider has stopped' still appear and I can't even to pass welcome guide!!!
Tablet is now useless, downgrade doesn't work.
Looks like Asus pulled the Lollipop update for the ME572C from their site.
I checked both the U.S. and Taiwan support sites (www.asus.com/us/Tablets/ASUS_MeMO_Pad_7_ME572C/HelpDesk_Download/ and www.asus.com/tw/Tablets/ASUS_MeMO_Pad_7_ME572C/HelpDesk_Download/). The Lollipop 5.0.1 WW_V12.14.1.9 build that came out in early April 2015 is nowhere to be found.
I hope Asus is going back to fix reported issues and...hopefully...go straight to 5.1 or 5.1.1 with the next update soon.
I checked also and noticed it was pulled after only being posted for a brief time. That is odd. I actually haven't had any issues with mine since updating to the lollipop build and actually have noticed a remarkable inprovement in my tablet since the last update. Of course, I did have to sacrifice my root to go to lollipop, but I was only using root to delete alot of the bloatware since the stock KitKat was slow and stuttered alot when new. It's not like we have an unlocked bootloader to flash custom roms with, so as long as they can make the stock firmware fast and smooth, I'm content to use it. Although, wouldn't it be cool if they pulled it and were gonna release the next update as a 64 bit version to take advantage of the 64 bit processor?
Related
Long story short, I was in Italy last week when the update was released. I was notified and installed without a hitch.
I came back to Mexico last Saturday. I was notified again of an update.
I didn't give it a second thought, figuring Google had released a hotfix for any bug they might have discovered.
Low and behold, Google downgraded my N7 back to 4.1.1 due to my geographic location!!!
I was rooted in before and the original 4.1.2 updated perfectly, as the 4.1.1 downgrade I was subjected to.
I tried the Force Stop / Clear Data trick. My tablet does detect the update, but upon reboot I get the firmware screen with the red warning sign.
I'll try the force stop / clear data trick again, as I've seen fellow xdaers getting a fully functional 4.1.2 N7.
Does anyone have any suggestions or recommendations?
Sent from my Nexus 7 using Tapatalk 2
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Vector_Calculus said:
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I just updated although I'm rooted but Im using the original ROM
See this thread too: http://forum.xda-developers.com/showthread.php?t=2648590&page=13
you have to unroot
You can unroot quite easily and apply the OTA then root again.
You shouldn't loose anything: download the original ROM you are currently running (the telus 4.3) and extract the 3 parts of the system image, then flash them using fastboot.
Let me know if that's not clear enough, I'll find the Step by step instructions for you.
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Vector_Calculus said:
It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
Click to expand...
Click to collapse
Yes, the naming scheme is quite confusing, but despite the fact that my German version is 176, US version is 174 and yours is 173 after updates, obviously they got exactly the same patches as you listed. No worries.
Vector_Calculus said:
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Click to expand...
Click to collapse
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
Battery drain is about the same as before. Maybe a factory data reset may help. I don't know if you lose root if you go this route..
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
There is a camera bug on 4.4.2 that keeps the phone running after exiting the app. A fix is o the way...
Heyo everybody! I just got this ota update message: "Essential system updates for google android - .7924"
Not sure what to do. I've had this tablet rooted for a while and I'm worried that updating will wipe out the root. Also, is it safe and/or possible to update the slate 7 extreme to lollipop and root it successfully?
Anyone?
Same here... I crash each time on reboot and have to reflash twrp and restore...
OTA...Update .. OK
I dont really care much for this tablet anymore until Lollipop arrives, like nVidia promised.
I updated in hoping to see Lollipop, but alas only for KIT KAT.
Update worked fine, and since I am on STOCK/NON-ROOTED, no issues whats so ever.
Fixed
ZiCott said:
I dont really care much for this tablet anymore until Lollipop arrives, like nVidia promised.
I updated in hoping to see Lollipop, but alas only for KIT KAT.
Update worked fine, and since I am on STOCK/NON-ROOTED, no issues whats so ever.
Click to expand...
Click to collapse
I finally managed to install the (kitkat) auto update and retain root status. As with previous updates (which I had forgotten about), I had to extract and modify the update header first, then flash it with TWRP.
Not attempted Lollipop yet.
Just for the purpose of tracking the rolling out process in the north America region, let's try collecting some date information when you receive the rollout. The process of this upgrade could become a helpful guideline for future upgrade events in the region! Models L04 and L14 might be involved. Let's also comment on your state, wireless service provider, if you are in the beta group and when you got the phone to see if anything is correlated. Please take a minute to fill out the form:https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Thank you!
Now, on the official Honor_USA social account, https://twitter.com/Honor_USA, N is coming on Feb 11th. Period.
Update: from Rox_honor, it's officially released on Feb 10th in the US. Some people have had this update already.
To force the update, you can check the method posted on Page 2, #16: https://forum.xda-developers.com/showpost.php?p=70992090&postcount=16.
Reserve for updating statistics, if possible. Again, the Google Spreadsheet to fill out is https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Feel free to add more columns if you think they are helpful.
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
chris23445 said:
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
Click to expand...
Click to collapse
There is one entry reporting received the update while on Straight Talk. We need to have more data in order to figure out the rollout sequence. GOOD LUCK!
i purchased the Unlocked Honor 8 from US (amazon). But I'm an indian user and I'm using it with an indian carrier . will i get the update as the other north american devices or do i have to wait longer
Did not get the update (FRD - L04)
But I forgot whether or not the L04 is international or US (i live in the US though)
yeah i havent gotten it either still says no updates available
I haven't received the update either on L04. I read on the other thread that it rolls out in small batches.
Edit: Here's the post: https://forum.xda-developers.com/showpost.php?p=70964112&postcount=392
Nothing on L04 AT&T yet. Purchased from NewEgg and first activated in December.
Got it 3 weeks ago. L04 from b&h.
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
yomomsbigpimp said:
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
Click to expand...
Click to collapse
Ahh, I was an idiot and had the same thing.
What happened is that I was rooted, and installed via Charles app, and it bugged out.
The reason for that is that TWRP can't install the stock ROM.
You need to get into fastboot, and reflash the stock recovery, and use it to dload the emui 4.1 file. Make sure you get the full package version.
After that it will be all wiped. You might run into a few errors but let the recovery do its thing.
You'll eventually be able to boot into the OS and then run the update normally.
I want to root my honor 8 on nougat, but I'm waiting for a patch from Huawei first because of all the bugs, just because of this.
Also I don't think rooting the honour 8 on nougat works that we'll yet, hopefully someone comes up with a method that doesn't suck so hard.
Hopefully they'll do it quickly.
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
yomomsbigpimp said:
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
Click to expand...
Click to collapse
I used the firmware finder tool for it. You can get it for Windows. It's somewhere around the forum, but you can probably Google it.
Once you get the full package you can extract the recovery.img from it.
Unlocked FRD-L04 bought from Amazon. Living in Argentina. Got update yesterday. Really happy with it.
Folks, if you are impatient, you can use the Firmware Finder to send the Firmware B360 (I am using the Jan 3 one) to your Updater for a full package update. More information can be found at https://forum.xda-developers.com/honor-8/how-to/news-huawei-firmware-finder-team-mt-t3550882
A few notes here from my personal experience:
1. Once you set up the proxy from the Finder's proxy app which should be downloaded after you enabled the "send firmware to updater" (check notification afterward), you then click on the latest firmware # and "send firmware to updater".
2. On the Setting/Updater, click the menu and use "Download full update package", which should direct you to a 2.27Gb package (not the 1.28Gb package, or you will not be able to login!) and click on the "Quick update" button. You may need to wait for a while to see this option. Up to now, you may not be able to download anything yet.
3. Go back to the wifi setting and turn on proxy setting to "None" again and reconnect with the wifi network. Now you should pause the Updater and then resume it. You should now be able to download the full package and install it.
4. After all the update process, it could be helpful to charge your phone without the screen turning on. This is told to be useful to optimize the battery performance immediately after the update. The phone might be slow in a couple of hours as optimizations are going on in the background. But everything will become normal afterward
Good luck!
bought L04 from newegg using it in Pakistan no update for me as of yet
This is all bulls*it. Same update we got in january, and by the way, it's buggy.
L04 here, bought from Amazon about a month ago. Running on T-Mobile US. Still no update yet.
Is there any way to change the white notification background? I prefer the old color scheme, Mich easier on the eyes at night.
Sent from my BTV-W09 using Tapatalk
Edit: Received update on US single SIM L04 on Straight Talk, ATT towers.
Hi,
I have a Pace with stock english rom and have been disappointed at lack of updates to ROM or supporting app. However it looks as though I may have received an OTA update this morning, but not completely certain. I was syncing with the app when the watch screen went black/off, hasn't happened before. There was a pause of a few seconds then the A logo appeared, but none of the swirly stuff like at power up just a couple of spinning circles, then a message "optimising apps" and counting through the number of apps just like a typical android ota update. The version number still says 1.30n like before and I can't see any obvious changes. Has anyone else seen this??
If users can post date and ROM version on this thread whenever they receive an OTA update on their Pace (Pace stock only please) it might be helpful to others.
if you're on 1.3.0n ... there was no update
Thanks 1imortal.
OK, if not an update what did I see? Where did the "optimising apps" message come from?
When was 1.3.0n rolled out, is it recent?
A little more detail please would be helpful.
1.3.0n was the initial version that came on the US variant of the watch, the Amazfit Pace, and was not updated since it came out.
what you have seen is probably a launcher crash with an update of apps, i've seen this on the CN version as well few times on my watch as well.
currently there is no definite ETA of the US OTA update, there are a lot of users that eagerly wait for it.
1immortal said:
1.3.0n was the initial version that came on the US variant of the watch, the Amazfit Pace, and was not updated since it came out.
what you have seen is probably a launcher crash with an update of apps, i've seen this on the CN version as well few times on my watch as well.
currently there is no definite ETA of the US OTA update, there are a lot of users that eagerly wait for it.
Click to expand...
Click to collapse
Many thanks, most helpful, makes more sense now. Will rejoin the patient queue for firmware and app updates that should develop the watch from good to great!
1.3.1 just came out. Just updated - new and custom watch faces, looks good. Some new run modes and a few optimizations.
Need help with 1.3.1m update
I recently flashed my ROM with full English ROM (https://forum.xda-developers.com/sm...utorial-convert-xiaomi-huami-amazfit-t3532508) I'm running 1.3.0n now. recently I got notification on 1.3.1m update but I can't update mine (failed to apply the update after downloaded and have to restart using the button).
Anyone has the same problem as I do? hopefully comes with solution too
Thanks in advance.
yes, have the same message. Think we have to wait...
Misuage said:
I recently flashed my ROM with full English ROM (https://forum.xda-developers.com/sm...utorial-convert-xiaomi-huami-amazfit-t3532508) I'm running 1.3.0n now. recently I got notification on 1.3.1m update but I can't update mine (failed to apply the update after downloaded and have to restart using the button).
Anyone has the same problem as I do? hopefully comes with solution too
Thanks in advance.
Click to expand...
Click to collapse
Kayman62 said:
Click to expand...
Click to collapse
Guys, the problem is solved for more than a week now. It is described in the first post of the thread (red bold text)..
Thank you, @Neuer_User
I ran into this thread after downgrading from your ROM to stock, and OTA always showed an error. Your post https://forum.xda-developers.com/showpost.php?p=71264431&postcount=599 solved this.