Hello guys,
I was just wondering why it takes a long time between getting update information from alternative sources to getting them from the phone update service?
I realize that there is always a window of 6 weeks or more between finding an update on firmware finder or web sources and getting it from huawei.
Does it mean it is still in testing - is that why FF says a firmware is not approved for installation? Surprisingly, people use HWOTA8 method to successfully install and use it without problems.
This is the fifth week since 371 has been released for 636yet not approved. Though Huawei is not doing too badly, I'm tired of getting Google patches a month and a half late.... & of course, I want to try the face unlock
My theory is this.
1. Whilst the firmware is probably pre tested, there's still the risk of bugs. By releasing to a small group at a time it makes it easier for Huawei to limit damage as if anything does go wrong, a limited rollout means a limited number of potential warranty claims, customer service calls etc.
2. Huawei's update servers may not be able to cope with all handsets calling in for updates at the same time. A staggered rollout will alleviate this stress.
Sent from my MHA-L29 using Tapatalk
Related
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
I just got my honor 8 and was wondering if I will get system updates when I upgrade the to the beta nougat?
I think that before rooting you should ask yourself what do you want to achieve. I used to root every phone that I had, usually in first two weeks after purchase. But now I have a phone and a tablet , both from Huawei and neither of them is rooted. Why? Because I came to the conclusion that I gained nothing with root and lost a lot. First there is no fully functional custom kernel for Honor 8 and the same is true for custom roms. So what is the point of rooting then? To have troubles with any single OTA and cutting off any chance of using secure apps (like Android Pay, other payment methods, Pokemon..). And profited only a chance to get rid of some system apps? Which can be frozen and removed from the home screen instead without rooting the phone.
I believe Android changed a lot with Marshmallow and every new release seems to be a step in the right direction. Huawei's EMUI is not a disorder in the concept, rather an improvement in many functionalities of the stock system (call recorder, close all apps, eye comfort screen, themes, phone manager....).
Honestly, I'm missing only two things to declare this phone as perfect: internet calling (voip, native sip, volte) and dark mode. But none of these could be solved with rooting. Internet calling should be implement (better: retrieved as the aosp has it already) by Huawei and dark mode might be created either by the producer or a skilled themer. Without rooting.
You probably would once the official version of Nougat for the Honor 8 is released. Personally, I would wait for the official release of Nougat rather than use the Beta. As it has allot of bugs and missing features on it.
DarkGuyver said:
You probably would once the official version of Nougat for the Honor 8 is released. Personally, I would wait for the official release of Nougat rather than use the Beta. As it has allot of bugs and missing features on it.
Click to expand...
Click to collapse
The beta's are actually pretty stable with very few bugs. And waiting on Huawei for the update is useless. Their updates are the slowest of any manufacturer I have ever seen. Use the Charles method and update as soon as possible. It's like a whole new phone.
https://forum.xda-developers.com/showthread.php?p=69885525
Sent from my FRD-L04 using Tapatalk
I have had my honor 8 for a few months now and I too normally root etc my phones as soon as I get them.
I have not rooted this one and am not planning on for a good while.
Im on the beta N program and I find that this together with the themes and fonts that I can use with out root makes the phone do everything that I want it to.
I'm going to keep my one as stock and make use of the updates that have been promised.
I can't see the point in rooting my phone just coz it's seen to be the thing to do with Android phones.
I do however have other phones that are rooted and I change the Roms weekly and am constantly playing with them.
Perhaps I'm happier keeping this unrooted coz I'm getting my fix elsewhere.
My advice would be root your phone if you need it to do something that requires root other wise enjoy your phone.
John
Sent from my Honor 8 using XDA Labs
clsA said:
The beta's are actually pretty stable with very few bugs. And waiting on Huawei for the update is useless. Their updates are the slowest of any manufacturer I have ever seen. Use the Charles method and update as soon as possible. It's like a whole new phone.
https://forum.xda-developers.com/showthread.php?p=69885525
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
I'm still betting Huawei/Honor is faster than any Cell Provider's OS Update releases. They take forever to come out as they have to wait for the device manufacturer to release their updates before they can modd them even further.
If your reason for rooting would be that you want Nougat now I would say wait. Personally I rooted my phone yesterday, and my reason was that i can't stand EMUI one day longer. I came from a Oneplus One and before that I have always rooted my phones. This time I waited for 4 weeks before I rooted, but could not live with the limited config settings I could change, so I rooted. No regrets.
But if you are fine with EMUI than take it easy and wait for the official update to Nougat.
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Paranoid "security" is purely meant to stifle open source community activity, nothing else (Maybe someone would need this if worked as CIA/MOSAD spy )
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
FullAccessForAll said:
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
Click to expand...
Click to collapse
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Funisillegal said:
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Click to expand...
Click to collapse
So how do you turn off automatic updates?
And isnt't enough simply to switch updates off from Android regular settings?
Settings->System->About Phone->Security updates (or somehow similar, watching just on my Polish menu)
Funisillegal said:
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Click to expand...
Click to collapse
Is anyone even working on a root for this device? Doesn't seem like it, I have one of these phones sealed in box never opened for the off chance someone picks up the charge and needs a stock firmware to toy around with given the phone was BOGO when I picked it up for my DIGITS line.
So far relying on ISLAND and IceBox, and it yields nice results.
Lg has equiped system with many quite useful and convenient features.
Not needed applications are just frozen.
However waiting for brealing from such utilities as KingoRoot.
So far disabled automatic updates hopefully making would-be exploits available for future versions of KingoRoot.View attachment 4747486
Hey guys,
I posted on the other threads but it seems like my concern shifts to be another.
First off: Yes I have tried switching regions with the tutorials. No nothing happened. I switched back to EuEx, no dualism because I don't need it.
Yes I tried every possible EU VPN Tunnel and updating OTA.
Nothing helped.
Now I have searched for my current Firmware, and there is no actual discussion about it. It is CPH2025_11_A.52 I am on the security Patch Level December 2020. So it came to my mind that it could actually be the firmware that prevents the updatingprocess. Is this possible?
With every other EU-Colleague of mine getting at least C59 with EuEX I'm starting to think it's just my phone.
Is there something I can do about it or do I have to wait for a flashable Android 11 zip? Which would ultimately leave me with selling the phone since I purchased it in regards to receiving an android 11 smartphone.
Thanks for reading in advance!
No problem with your version ,its just Oppo s way of doing things.I have cph 2025.11.A50 november security patch.
I reached them and they said i should take my unit to service ,i asked them why?its not broken !
Very wierd solution.
My phone works like a charm ,great performance ,good battery life ,so im happy with the software.
P.s bought phone from Switzerland.
@andreiselegean1984 @CaptainRage while it may not be broken on the hardware level there definitely seems to be something wrong with it, so sending it in is not that weird a solution imho. There surely is some sort of repair service in your country that acts as an official Oppo partner for warranty repairs, so why not just contact them and see if they can help by just flashing the newest software onto it and be done with it. The only hassle being that you'll have to do without it for a couples of days but maybe you still have one of your older phones that you can use instead for the time being...
Well Oppo doesn't seem to be cooperating that much:
We are sorry to know that you didn’t receive the ColorOS 11 update on your Find X2 Pro just yet.
In order to clarify this for you, please allow us to offer you a background explanation.
To make sure everything of the new version can run smoothly and reduce the unnecessary risk of the end-user, the ColorOS 11 update is released in batches. This is a protective measure used in global leave for all the new software versions.That’s why a certain amount of devices don’t receive the update on the announced date. But don’t worry! As your satisfaction is our priority, we at OPPO are doing our best to release the update for your phone as soon as possible. Rest assured that you will receive ColorOS 11 soon.
I appreciate your understanding and wish you a wonderful day!
Click to expand...
Click to collapse
CaptainRage said:
Well Oppo doesn't seem to be cooperating that much:
Click to expand...
Click to collapse
This is just the usual BS the customer service gives you, forget about that. There have to be companies in your country that are official Oppo service partners which do all the repairs that are eligible for warranty. Contact one of them directly and tell them what the problem is and see if they accept it as a warranty repair.
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com
I joined the beta program
BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.
Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....
Google is having problems
This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly
BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com
Yeah I am on December update very annoyed with Google nothing has changed
Deleted
That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.
Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Also mine show November as last play service update (I'm on the beta). Italian unlocked phone
Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet
EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...
I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?