I've never seen such device vagueness \ lack of specifics data.
OP Community forums useless.
I purchased from OP USA & have not activated cellular service yet.
Settings list model OPD2203 OS 13.1, no geography. Build # opd2203_13.1.0.519(EX01)...already contains Multi-Connect.
No other model name listed in web search.
System Updater says OS up to date, while
Oxygen Updater just added this device, listing Euro & Indian variants, labeling this the latter,
and presenting update opd2203_13.1.0.544(EX01) 2023-06-03 (...adds Multi-Connect support... nothing re any monthly Android Security Patch)
IF I label it European, it throws error message and removes presented update.
Tablet was released w\o Multi-Connect btw, so that higher upgrade # claiming to add Multi-Connect makes no sense (if lower version # already has it).
I'm clueless here. ¿Any thoughts? Thanks.
If you read the announcement in the Oxygen Updater app declaring that the device is now supported, you'll find that it also says:
Both full & incremental OTA ZIPs for A.12 are available in the app, except for global/NA, because we're not yet sure of that regional variant's model number. If you have this device in the US, please email us at [email protected] with a screenshot of the "Device" tab in our app.
Click to expand...
Click to collapse
I'd imagine after you email them the requested info, the proper firmware will be added to the app.
Thank you for that. Except that all seem to have the same model number. I'll send, maybe I'm missing something obvious.
Just got presented ota with same version number update already being presented for days by Oxygen Updater.
It's description is strange though- my Pad already had full Multi-Connect.
Related
When I speak to Samsung, they deny any chance of new firmware until FroYo is released.
The Samsung Russia website does not (or at least didn't) list the Galaxy S as being available.
So all these firmwares Im seeing here, how genuine are they, and how come they're all from Russia?
Additionally, can I take a copy of my current firmware just in case?
My thoughts exactly. No one knows where these firmware updates are coming from but they are signed with Samsung's signing key else they wouldn't be able to be applied to these phones without getting root access first.
I think (bit of a guess) either these are leaked developer builds of the firmware (which will also explain why they are updating so quickly) or someone has managed to acquire Samsung's signing key. They are recompiling the firmware from Samsung's publicly available source code and putting them out with the updates and fixes.
I think it's the former option but this is just me speculating. If they were coming from Samsung officially then why isn't Samsung making them available via their own website which would have credibility. Even if they were unpolished firmware releases, they could always release them as Beta.
A lot of us have been wondering. Here's my take on this:
http://forum.xda-developers.com/showpost.php?p=7087406&postcount=123
If someone with more inside knowledge could enlighten us, it would be great.
New update just pushed to my Verizon S6 Edge. Not sure what was in it yet. Can't seem to find a changelog anywhere. I'll do some more looking and post back if I find something. May be just another Security Update?
Software Version: NRD90M.G925VVRU4DQF3
This software update provides:
The latest Android® security patches
Fixes ringback tone playback to non-Verizon Wireless phones
Actually after I used VZW software upgrade assistant (I switched to Tmobile, so can not do update by OTA), the version is DQH1, not DQF3.
Android Safety Patch is 8/1/17.
[email protected] said:
Actually after I used VZW software upgrade assistant (I switched to Tmobile, so can not do update by OTA), the version is DQH1, not DQF3.
Android Safety Patch is 8/1/17.
Click to expand...
Click to collapse
I believe the updates are specific to your carrier. This update was specific to Verizon users. If you are now on T-Mobile, you should receive a different update when T-Mobile issues one.
I can not receive update from Tmobile. My phone is from Verizon. They are different in some hardware I believe.
Zelmo88 said:
I believe the updates are specific to your carrier. This update was specific to Verizon users. If you are now on T-Mobile, you should receive a different update when T-Mobile issues one.
Click to expand...
Click to collapse
I own the Canadian P20 pro variant (CLT-L04) and just installed a recent official OTA firmware update for it - version 8.1.0.111 (from 8.1.0.009). My device started with 8.1.0.007.
I've been debating about rebranding in order to get the more recent firmware updates which appear to be up to version 8.1.0.132 (?) worrying that I was missing the more recent features.
But after checking out the changes in this firmware I realized that I have many of the same features of the supposedly more recent firmwares such as:
1. The new zoom button in the camera interface placed at the bottom of the screen in the shape of a square.
2. The new slow motion box that detects movement and starts the super slow motion automatically.
3. ISO select up to 102400 is Pro mode.
4. Camera defaults to 2x mode in aperture mode (not a fan on this)
5. The HiTouch feature accessible through the camera (the eyeball icon - top left) or by touching the screen with two fingers
6. Latest security patch is for June 1st, 2018 (this is behind some other firmwares I believe that have July patches?)
7. Selfie beautification is much lower .
I'm not sure what other features I'm missing out on compared to the supposedly more recent firmwares but these seem very similar to what are being reported in firmware 8.1.0.132.
Does this mean that Huawei releases different features by region even if the firmware has the same version number? In other words, firmware version 8.1.0.11 in Canada will have features that 8.1.0.11 in another country does not? This means one cannot directly compare firmwares by version number alone and assume they are equivalent in terms of features and changes across devices.
Anyone else running 8.1.0.11 on any other variant who can check whether they also have the features I've observed in my firmware version?
So confusing :
In any case, I'm much less concerned about rebranding now that I seem to have some of the more recent firmware changes.
I'm not 100% sure, but my opinion is that different regions elaborate in different speed the base firmware.
I am not speaking about minor country differences, but major like: Eu, China, Russia, US, Canada etc.
For example:
european firmware numbers are far ahead of china firmware numberings, however, eu firmwares lack a lot of functionality, that cn firmwares had already
(eu fw CLT-L29C432B132 has the functions, that CLT-AL01C00B112 cn firmware already had)
So i am assuming, that this happens in your case.
One prove is FF - look at the changelogs: despite one has july patch, however another from june patch has a lot more improvements
And about FF speaking: always take a look at version numbers ex:
CLT-L04C792B113 (8.1.0.113) FullOTA-MF 3.43 GB 2018.07.11 3085 1604 version nr: 154641 1
CLT-L29C432B131a (8.1.0.131a) FullOTA-MF 3.3 GB 2018.07.05 2943 1604 version nr: 150210 1
How did you get 111 in Canada? Ota won't update past 109 for me
viper98 said:
How did you get 111 in Canada? Ota won't update past 109 for me
Click to expand...
Click to collapse
u the same viper98 from rfd?? lmao
for me, im on 109 as well. No available updates.
Thanks tamaskurti for your observations and explanation.
As for other Canadians on firmware 109 all I did to get the update is manually check by pressing the "check for updates" button in the system ->system updates page.
I use firmware finder to check for new firmwares only. The OTA updates come a little more than a month after the date that is listed in the firmware finder description.
E.g., firmware 111 was dated June 14th and I received it July 20th.
UPDATE: There is yet another update on FF for version 113 for the Canadian model. It is dated July 11th so I expect to see the OTA update middle of August if this pattern holds.
BTW I'm with Koodo mobile (Telus) and bought the phone through them. Maybe they are faster to approve the firmwares than Bell or Rogers and thats why some of you are getting it later? Just a guess.
I'll try to keep this thread updated with any other firmware changes that I notice when I receive . 113
Weird. I checked with a koodo sim in Thursday and it didn't find anything
oraos said:
Thanks tamaskurti for your observations and explanation.
As for other Canadians on firmware 109 all I did to get the update is manually check by pressing the "check for updates" button in the system ->system updates page.
I use firmware finder to check for new firmwares only. The OTA updates come a little more than a month after the date that is listed in the firmware finder description.
E.g., firmware 111 was dated June 14th and I received it July 20th.
UPDATE: There is yet another update on FF for version 113 for the Canadian model. It is dated July 11th so I expect to see the OTA update middle of August if this pattern holds.
BTW I'm with Koodo mobile (Telus) and bought the phone through them. Maybe they are faster to approve the firmwares than Bell or Rogers and thats why some of you are getting it later? Just a guess.
I'll try to keep this thread updated with any other firmware changes that I notice when I receive . 113
Click to expand...
Click to collapse
Looks like it updated to .114 now. Just an FYI
Being behind on updates feels bad
I just got 111 pushed today
tried on my koodo sim
still nothing there either
With Bell, just received the 111 update. How do we go about rebranding? Wouldn't mind trying a new Rom
Hi All,
I've had a google and can't find anything about this so wondering if anyone knows what is up with firmware finder? Loads of new firmwares appeared today all at once.
The attached screenshot is from the CLT-L09C782 version but seems to be happening to other versions too.
My guess is that it's now showing beta's that we didn't previously have access to.
How are we supposed to work out which to use going forward? I would love to force a newer version but need it to be certified for google pay etc.
Type on phone dialer: *#*#2846579#*#* (ProjectMenu)
From that go to 2. Veneer Information.
Than 1. Version Info.
Now scroll down till you will find: Product Component version, Base Software Version.
I am now on CLT-AL00C00B181 (pie b181).
However, it appears to mine version too: Product-CLT-LGPR1-CHN 9.0.0(P), and CLT-LGRP1-CHN 9.0.0.181.
So I suppose, that the new names stands for simplifying the huawei firmware namings.
It will not be multiple versions but 2 (maybe): CLT-LGRP1 for asian market (CHN) and CLT-LGRP2 for the rest (OVS).
But again this is my logic.
Anyway, I didn't know how update, since those new firmwares contains not 2 but just 1 zip file (full_base).
Just an update:
If you chose in FF the model name: CLT-LGRP1 (for CHN) or CLT-LGRP2 (for the rest) you will find the same firmware version as earlyer with older name convention. (This stands for PIE only)
Example: CLT-LGRP1-CHN 9.0.0.181, 167, 156, ... 110. Same versions as earlyer just with modified names.
tamaskurti said:
Type on phone dialer: *#*#2846579#*#* (ProjectMenu)
From that go to 2. Veneer Information.
Than 1. Version Info.
Now scroll down till you will find: Product Component version, Base Software Version.
I am now on CLT-AL00C00B181 (pie b181).
However, it appears to mine version too: Product-CLT-LGPR1-CHN 9.0.0(P), and CLT-LGRP1-CHN 9.0.0.181.
So I suppose, that the new names stands for simplifying the huawei firmware namings.
It will not be multiple versions but 2 (maybe): CLT-LGRP1 for asian market (CHN) and CLT-LGRP2 for the rest (OVS).
But again this is my logic.
Anyway, I didn't know how update, since those new firmwares contains not 2 but just 1 zip file (full_base).
Just an update:
If you chose in FF the model name: CLT-LGRP1 (for CHN) or CLT-LGRP2 (for the rest) you will find the same firmware version as earlyer with older name convention. (This stands for PIE only)
Example: CLT-LGRP1-CHN 9.0.0.181, 167, 156, ... 110. Same versions as earlyer just with modified names.
Click to expand...
Click to collapse
Thank you for the explanation. Hopefully someone will figure out how to force the updates in the near future. I liked the Firmware Finder eRecovery option so hopefully that can be adapted to work.
This would make sense, well spotted. Relatively unified os.... Before the operators get their hand son it. However the naming makes it difficult to know which to install via ff as there's many different versions eg 204 211 all released on same day....
Sent from my CLT-L09 using Tapatalk
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
Also doesn't this go against the arrangements eg seperate regions..... One specifically for the UK?
Sent from my CLT-L09 using Tapatalk
blufreak said:
This would make sense, well spotted. Relatively unified os.... Before the operators get their hand son it. However the naming makes it difficult to know which to install via ff as there's many different versions eg 204 211 all released on same day....
Sent from my CLT-L09 using Tapatalk
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
Also doesn't this go against the arrangements eg seperate regions..... One specifically for the UK?
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
It certainly is confusing now there's no way to tell which version is for which region of which device. No way of knowing if it's L09, L29, C782 etc.
Hopefully someone will figure it our or the FF people will update the app so show extra details if that is possible.
Probably been done specifically to block people using the likes of ff on behalf of the networks cos they had a tantrum [emoji23]
Sent from my CLT-L09 using Tapatalk
PsychoMania said:
Thank you for the explanation. Hopefully someone will figure out how to force the updates in the near future. I liked the Firmware Finder eRecovery option so hopefully that can be adapted to work.
Click to expand...
Click to collapse
I didn't get to check it with eRecovery method, but it worked for me with modified HiSuite method without any problem (updated C432 from .163 to .195).
For now I didn't find any of the .2XX builds to be approved for installation.
So out of curiosity (boredom) I've done a bit of browsing with the help of Google translate, it seems lgrp is the component level name given to the devices. And upon checking on FF only .211 has been "approved for installation" so I'm currently downloading the file directly to check filenames as it seems the uncompressed file may still have the region number in it. If I don't report back...... My phones dead lol
Sent from my CLT-L09 using Tapatalk
So file contents give no indication of specific region, and even accepted and allowed updates fail once reach the erecovery stage.... Just getting "getting package info failed" over and over.
So not only are Huawei **** at releasing the updates but they're pretty adept at blocking us from taking alternate routes
Sent from my CLT-L09 using Tapatalk
It's been a few months after buying the ROG 2 and I updated to Android 10. Now I've got another update but can't seem to download it regardless using mobile data or wifi. Is there something I should check before updating? Didn't have any issues upgrading to android 10 but the I'm stuck at the next update. Just keep getting the error " System Update failed. Your device has reverted to it's original configuration."
Hi, same here! (Italy)
I posted this https://forum.xda-developers.com/rog-phone-2/help/phone-modified-firmware-t4135801.
As I wrote in the post, I sent a mail to Asus, they asked for build number details and they said my phone has a "custom firmware" I installed (???? never done that) voiding warranty. So they'll fix it but as out of warranty.
In that post you can check the build infos I've right now. Are they the same as yours?
darkmage1975 said:
Hi, same here! (Italy)
I posted this https://forum.xda-developers.com/rog-phone-2/help/phone-modified-firmware-t4135801.
As I wrote in the post, I sent a mail to Asus, they asked for build number details and they said my phone has a "custom firmware" I installed (???? never done that) voiding warranty. So they'll fix it but as out of warranty.
In that post you can check the build infos I've right now. Are they the same as yours?
Click to expand...
Click to collapse
Yeah all the info is the same as yours but I've never rooted the phone. Heck the only update I did was updating from 9 to 10
sainantha said:
Yeah all the info is the same as yours but I've never rooted the phone. Heck the only update I did was updating from 9 to 10
Click to expand...
Click to collapse
Same here. Bought in May, auto updated (via FOTA) in June (from Android 9 to 10), and this is the second update. I don't know what to say. I hope someone else could find a solution.
Same problem, same versions of the system. Unfortunately I also contacted asus and they told me the same thing ... I hope they have not taken away the guarantee.
Do you guys have the Tencent version of the phone? If so, that could be the reason Asus says it's been modified. A lot of third party retailers will still the cheaper Tencent version with modified global ROM installed.
TikiThePug said:
Do you guys have the Tencent version of the phone? If so, that could be the reason Asus says it's been modified. A lot of third party retailers will still the cheaper Tencent version with modified global ROM installed.
Click to expand...
Click to collapse
Pretty sure I'm not using the tencent version
Anyways found a possible fix
Download the zip file from the Asus page and manually update in your phone. It will fix the issue
darkmage1975 said:
Same here. Bought in May, auto updated (via FOTA) in June (from Android 9 to 10), and this is the second update. I don't know what to say. I hope someone else could find a solution.
Click to expand...
Click to collapse
I was chatting with Asus support and they directed me to the asus page to download the update and update manually in the phone. While I was updating the zip file I noticed the FOTA update running alongside of it and I was able to update it. Hope this works for you.
sainantha said:
I was chatting with Asus support and they directed me to the asus page to download the update and update manually in the phone. While I was updating the zip file I noticed the FOTA update running alongside of it and I was able to update it. Hope this works for you.
Click to expand...
Click to collapse
Thank you, same here. They directed me to this file https://dlcdnets.asus.com/pub/ASUS/..._I001_1-ASUS-17.0240.2007.27-1.1.204-user.zip
but since I insisted that I had not installed any custom firmware, they replied "the version you reported is not among the firmware files but in the Open Source section, this does not mean that you have installed an unofficial firmware" so no invalidation of the warranty.
Anyway ... the only firmware that was installed on my phone, was downloaded through FOTA ...
darkmage1975 said:
Thank you, same here. They directed me to this file https://dlcdnets.asus.com/pub/ASUS/..._I001_1-ASUS-17.0240.2007.27-1.1.204-user.zip
but since I insisted that I had not installed any custom firmware, they replied "the version you reported is not among the firmware files but in the Open Source section, this does not mean that you have installed an unofficial firmware" so no invalidation of the warranty.
Anyway ... the only firmware that was installed on my phone, was downloaded through FOTA ...
Click to expand...
Click to collapse
Could be due to the Android 10 update, prior to that everything was smooth sailing and issue free