Database Develop

Install EMUI 5 on EVA L09C521B140

As the title says, how can I install the android 7 OTA on my P9 EVA L09C521B140? In the post http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
I saw that the OTA for NXT-L09C521B140, it serves me the same? In what changes?
Thank you very much

I'm interested in this as well. I'm assuming you're interested in unbranding your phone as I am? Got it from a carrier, right?
If you find out anything regarding this please do let me know.

ivanfenoy said:
As the title says, how can I install the android 7 OTA on my P9 EVA L09C521B140? In the post http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
I saw that the OTA for NXT-L09C521B140, it serves me the same? In what changes?
Thank you very much
Click to expand...
Click to collapse
That post is old and it hasnt been updated it ages, if you want to know the latest firmware for your C521, best to download an app called Firmware Finder and check in there, B361 is the official released Android 7 firmware.

Z-Blade said:
That post is old and it hasnt been updated it ages, if you want to know the latest firmware for your C521, best to download an app called Firmware Finder and check in there, B361 is the official released Android 7 firmware.
Click to expand...
Click to collapse
Hi, thanks for replying.
This is only the second day I have this new phone. I got it from my carrier so it has their brand at boot, the crappy bloatware they tend to put etc.
What I would like to do (at least until the devs manage to release a stable CM version for the phone) I'd like to get the OFFICIAL stock rom (unbranded, like bought from a store)
Could you point me somewhere where I could find how to do it, where to start etc? I'm all for learning myself but a start-point would be nice.
If I'm not mistaken, the model is EVA-L09 so C521 would be the variant? and B140 the firmware version, correct? And what's with the "cust" version at the bottom? carriers firmware?
Also, I've been reading and apparently NOUGAT is still in beta for these phones? So I guess I'd like to update to latest MM, and then update whenever they decide to release OTA.
Thanks in advance.
EDIT* TL;DR, Basically, I want to unbrand the phone. Remove my carriers bloatware. Just like a store bought phone.

SideSkroll said:
Hi, thanks for replying.
This is only the second day I have this new phone. I got it from my carrier so it has their brand at boot, the crappy bloatware they tend to put etc.
What I would like to do (at least until the devs manage to release a stable CM version for the phone) I'd like to get the OFFICIAL stock rom (unbranded, like bought from a store)
Could you point me somewhere where I could find how to do it, where to start etc? I'm all for learning myself but a start-point would be nice.
If I'm not mistaken, the model is EVA-L09 so C521 would be the variant? and B140 the firmware version, correct? And what's with the "cust" version at the bottom? carriers firmware?
Also, I've been reading and apparently NOUGAT is still in beta for these phones? So I guess I'd like to update to latest MM, and then update whenever they decide to release OTA.
Thanks in advance.
EDIT* TL;DR, Basically, I want to unbrand the phone. Remove my carriers bloatware. Just like a store bought phone.
Click to expand...
Click to collapse
If you look through the guide section of this forum, you will find what you been looking for. If you are looking at debranding and getting on to Nougat, you can follow this guide. Also, Nougat (EMUI 5.0) is now being officially rolling out but at a very slow pace.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523

Huawei Mate 20 Pro Australian Discussion

I thought I'll make this thread for the Australian Mate 20 Pro Owners.
As we may all know already, Optus and other ozzy telcos are extremely slow with releasing there updates for our devices, it's very frustrating as we have to wait for important updates and fixes.
In this thread I'll love to hear from other Australians and there opinions on this matter. Also to discuss firmwares that have been flashed from other regions on our devices etc
All topics about our devices are all welcome

I have the L29. Currently with Telstra (Prepaid)
My last OTA update was 168 which I received around the end of December.
I recently unlocked my bootloader and updated to 182 following a guide in these forums
I also rooted my device using the same guide.
I don't really have too much to say on the speed of our updates, as I've only had my Mate 20 Pro since the 28th of Dec. It's my first android phone and I'm loving it so far. I've been wanting to get away from Apple for years, but the jailbreaking scene kept me with them. Now that the scene is almost dead I decided it was time.
So now I'm getting my head around rooting.

LYA-L29 here.. C636 SPCSEAS region on mine.
Have done the fh 171 update.. Now on unlocked bootloader and rooted 182. Tried the custom 182 rom but no joy with magisk in hiding safety net stuff for Google pay.. However with the stock 182 I was able to hide the safety net checks with magisk help.
What might be of interest to people to is I've been able to downgrade back to 171 and relock bootloader which previously was said could not happen. Back on 182 though now.

Currently running an L29 bought from eBay AU but originated in the UK as far as I can tell (based on the charger mains plug)
Latest version It'll update to is .168, it started off at .109 and has done 2 updates in the 2 days I have had it.
I've ordered a BL code and will look at rooting once I have it, there seem to be 2 different guides in this forum at the moment. Still working out which way to go. One of the methods definitely involves rebooting into recovery every time in order to get root, not sure if the other method does as well.

I find the 182 firmware to be a great one, I have noticed more of a battery drain on this one but nothing to really worry about.
I find it awesome that the hwota method works and we are now able to flash the same or higher firmwares with pretty much ease now. To be honest everytime I fiddled with my phone before the hwota method came out I would stuff something up then use funky Huawei to bring it back to life lol that was beginning to be an expensive venture haha.
This device shows alot of promise, I am currently using magisk and have used modules to pass safety net. Also used titanium backup to remove some system apps I never use. I froze Huawei home and now use nova launcher and used the Google framework module to install the Google phone and contacts app which I find much better. I am happy to say I now have the device exactly where I want it to be. I have also added a 64gb Huawei nano memory card to my device, as it may be expensive I thought why not. Now all my photos get saved to memory card

Minotaur said:
Currently running an L29 bought from eBay AU but originated in the UK as far as I can tell (based on the charger mains plug)
Latest version It'll update to is .168, it started off at .109 and has done 2 updates in the 2 days I have had it.
I've ordered a BL code and will look at rooting once I have it, there seem to be 2 different guides in this forum at the moment. Still working out which way to go. One of the methods definitely involves rebooting into recovery every time in order to get root, not sure if the other method does as well.
Click to expand...
Click to collapse
The patched_boot.img method is what I'm using basically when the phone reboots it automatically boots up the patched_boot and goes straight into the os, you don't even notice it which is great

souljasteve84 said:
The patched_boot.img method is what I'm using basically when the phone reboots it automatically boots up the patched_boot and goes straight into the os, you don't even notice it which is great
Click to expand...
Click to collapse
Which one is that? Can you provide a link to the thread/guide?
Cheers.

Minotaur said:
Which one is that? Can you provide a link to the thread/guide?
Cheers.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-20-pro/how-to/guide-unlocking-bootloader-magisk-root-t3885422

Minotaur said:
Which one is that? Can you provide a link to the thread/guide?
Cheers.
Click to expand...
Click to collapse
Basically grab the recovery_ramdisk IMG and use that in magisk to get a patched_boot.img that would be the best way but in the guide it's got all the info you need there.

souljasteve84 said:
Basically grab the recovery_ramdisk IMG and use that in magisk to get a patched_boot.img that would be the best way but in the guide it's got all the info you need there.
Click to expand...
Click to collapse
According to that page, that method requires booting into recovery mode all the time?

Minotaur said:
According to that page, that method requires booting into recovery mode all the time?
Click to expand...
Click to collapse
It doesn't it does it automatically you won't even notice

LYA-L09 from Optus here still on .122, with .146 due end of this month. Optus update schedule is a joke. As soon as FH .182 is safety net approved, I'm doing it. Don't really want to pay the $70 to unlock bootloader but will likely do that too eventually.

Yes Optus is a joke. Hopefully they start working on .171 which is supposed to have a unlock bootloader although I am sure optus will modify it to stay locked.
Sent from my HUAWEI LYA-L09 using XDA Labs

Optus are still stuffing everyone around with not yet releasing an almost 2 months old firmware. All they can do is give you a recorded message.
They certainly are the most pathetic telecommunications company.
Sent from my HUAWEI LYA-L09 using XDA Labs

It seems to have come to light that optus won't be supplying firmware updates, 2 reasons were mentioned today
1 is that huawei have not issued a software licence and will not provide optus with firmware.
2 is that optus have abandoned huawei firmware updates because of the huawei 5G and US ban with regards to spying.
All the times optus have mentioned testing firmware for the mate 20 Pro has been lies, it now is apparent that they were never testing anything.
This matter via being addressed by me in writing to both Huawei and optus, if they fail to respond or provide a firmware update solution. Consumer Affairs Victoria will be filing a complaint against them con VCAT Court.
Sent from my HUAWEI LYA-L09 using XDA Labs

Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?

Minotaur said:
Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?
Click to expand...
Click to collapse
It's got the optus splash screen and has firmware modified by optus and huawei for optus specific handsets.
Sent from my HUAWEI LYA-L09 using XDA Labs

Minotaur said:
Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?
Click to expand...
Click to collapse
No, updates are handled by the firmware supplier(Optus) no matter what SIM you put in it
Optus is awesome
Android Software Updates - 07/12/2018
On Hold, waiting for updates on DBU
Click to expand...
Click to collapse
Android Software Updates - 21/12/2018
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Estimated release: Early – Mid January
Click to expand...
Click to collapse
Android Software Updates - 07/01/2019
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Predicted release: Late January
Click to expand...
Click to collapse
Android Software Updates - 29/01/2019
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Predicted release: Late January
Click to expand...
Click to collapse
Android Software Updates - 07/02/2019
Upgrade to 9.0.0.183
Status: Testing
Estimated testing completion timeframe: mid-late February
Click to expand...
Click to collapse
So what, they get so far and over a month just to give up on .146 ... I can't wait for another month of testing .183 just for them to give up on that

Xalies said:
No, updates are handled by the firmware supplier(Optus) no matter what SIM you put in it
Optus is awesome
Android Software Updates - 07/12/2018
Android Software Updates - 21/12/2018
Android Software Updates - 07/01/2019
Android Software Updates - 29/01/2019
Android Software Updates - 07/02/2019
So what, they get so far and over a month just to give up on .146 ... I can't wait for another month of testing .183 just for them to give up on that
Click to expand...
Click to collapse
They are not testing .183 they are supposed to be working on .188 but at this point optus don't have a software licence from Huawei, and huawei are refusing to release the firmware until they get a licence approved.
This could be months or not even happen at all
They also have never been testing any firmware because huawei have never released any to them for testing as to date.
Here is the message I received from Optus last week.
Hey Darren,
This is what I recieved internally from our Tech devs,
For Australian carriers, Huawei will release MR every 2 months. They do not know the release details until about 1 month before the release. They have skipped .146 and .183 because they did not meet Optus requirements. We are going to get .188 for testing which is the later version than .183. The only way for the customer to get .183 is to buy an open market handset.

So we're all still on .122 ?
I want to say "un ****ing believable" but it's really not.
It's simply not good enough

N00B question, N960W running Rogers bloat, is there a generic universal FW?

I just got my hands on a Note 9 that was bought from Rogers and therefore has the Rogers rom.
I can use ADB or PDP to remove the bloat, but for the sake of simplicity, I would much rather just use a standard universal rom. I remember being able to do this when I had my Note 7 but its been a while and I'm forgetting the process. I remember using Odin lol.
Any advice and help is greatly appteciated! Also, I tried searching but XDA search NEVER seems to show results, EVER.

imatts said:
I just got my hands on a Note 9 that was bought from Rogers and therefore has the Rogers rom.
I can use ADB or PDP to remove the bloat, but for the sake of simplicity, I would much rather just use a standard universal rom. I remember being able to do this when I had my Note 7 but its been a while and I'm forgetting the process. I remember using Odin lol.
Any advice and help is greatly appteciated! Also, I tried searching but XDA search NEVER seems to show results, EVER.
Click to expand...
Click to collapse
I'm almost certain the SM-N960U1 firmware will work on your phone.
However,you may lose some carrier-specific functionality (WI-FI Calling/VoLTE/VVM/etc....) by doing so.
I have no direct knowledge of Rogers,but,there is a dedicated Canadian Note 9 thread you may want to take a look at before proceeding:
https://forum.xda-developers.com/ga...te-9-canadian-thread-rumours-pricing-t3826820
EDIT:
@imatts
Taking a look at this this site (Updato),it looks like there may be Canadian-specific unlocked/SIM-Free (SM-N960W) firmware:
https://updato.com/firmware-archive...&rpp=15&r=SPC,XAC&order=date&dir=desc&exact=1
Again,my knowledge of Canadian versions & carriers is non-existent,so,please take a look in the thread I linked above for guidance.

KOLIOSIS said:
I'm almost certain the SM-N960U1 firmware will work on your phone.
However,you may lose some carrier-specific functionality (WI-FI Calling/VoLTE/VVM/etc....) by doing so.
I have no direct knowledge of Rogers,but,there is a dedicated Canadian Note 9 thread you may want to take a look at before proceeding:
https://forum.xda-developers.com/ga...te-9-canadian-thread-rumours-pricing-t3826820
EDIT:
@imatts
Taking a look at this this site (Updato),it looks like there may be Canadian-specific unlocked/SIM-Free (SM-N960W) firmware:
https://updato.com/firmware-archive...&rpp=15&r=SPC,XAC&order=date&dir=desc&exact=1
Again,my knowledge of Canadian versions & carriers is non-existent,so,please take a look in the thread I linked above for guidance.
Click to expand...
Click to collapse
Thank you. Another noob question (if anyone else is reading this, feel free to also help!)
I see a ton of random characters after the N960W, what do they mean? How do I know which one to choose, and also, whats the difference between the XAC and SPC versions?

imatts said:
Thank you. Another noob question (if anyone else is reading this, feel free to also help!)
I see a ton of random characters after the N960W, what do they mean? How do I know which one to choose, and also, whats the difference between the XAC and SPC versions?
Click to expand...
Click to collapse
I can help you there. I wrote a guide to decode the build number. It was written for the N960U, but still applies to the N960W.
---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------
You can tell what version of Android it is just by the build number. You can also tell if each update just contains the updated security patch, or if new features were added or updated.*
The first character (S or U) tells you if it's a security patch or a feature update. S = Security Patch and U = Feature Update (features added or changed)
The second character (a number) tells you bootloader version. This is important to know when upgrading and downgrading OS versions. You can NOT downgrade the bootloader. 1 = Bootloader V1, 2 = Bootloader v2, etc...*
The third character tells you the Android version. This is different for each Galaxy device. A is the Android version that device 2as released with. (For the Note 9 A=Oreo; C=Pie) B will likely be newer versions of Oreo, possibly with an updated bootloader. Z is for official Samsung BETA program builds.*
The fourth character is the year of the build (R=2018, S=2019). This is the same across all Galaxy devices.
The fifth character is the month of the build. This does not indicate what security patch it contains, only what month it was built. (A=January, B=February). Again, same across all Galaxy Devices.*
The sixth character is just the sequence of builds that month (1-9, then A-Z)
SO
S - Security Patch
1 - Bootloader V1
A - Oreo
R - 2018
J - October build
9 - 9th build in October
and*
U - Feature update
1 - Bootloader V1
C - Pie
R - 2018
L - December build
2 - 2nd build in December
and
U - Feature update
1 - Bootloader v1
Z - Official Samsung BETA program build
R - 2018
K - November build
P - 25th build in November
So let's break down my current build number, N960U1UEU1ZRLL
N960U1 - Build is for the Factory unlocked U1 model
UE - Honestly I have no idea, LOL
U - Features updated or added
1 - Bootloader V1
Z - Official beta build
R - 2018
L - December*
L - 12th build in December
Make sense?

all canadian firmwares I've seen are identical. the trick would be to change your sales code to XAC(unbranded Canadian region code). and just flashing the XAC firmware wont do squat as it still contains all carriers because its multi csc and your sim card will still end up being detected and get its carriers bloat. (SPC = PC mobile , president's choice? lol)
i have no experiance with flashing u1 on a W.
but if it works, loosing csc specific features and other stuff might not be worth it in the end just to debloat.
Mr. Orange 645 said:
UE - Honestly I have no idea, LOL
Click to expand...
Click to collapse
pretty sure its United States' region identifier

bober10113 said:
pretty sure its United States' region identifier
Click to expand...
Click to collapse
You may be right. I honestly haven't researched that part of the build number.
Edit:. It appears that's correct. I can find a list of region codes, but ironically none of them include US region codes. But that has to be the region code.
The N60U1 firmware all show a region code of UE, and the carrier branded N960U show a region code of SQ.
Thanks for the info!!

Mr. Orange 645 said:
I can help you there. I wrote a guide to decode the build number. It was written for the N960U, but still applies to the N960W.
Click to expand...
Click to collapse
Dude I am so thankful that you took the time to break this down for me, and you have helped me dramatically. Makes perfect sense, and I've gone ahead and downloaded the proper fw!
I downloaded the XAC version. It says 4hrs til complete though -_-

imatts said:
Dude I am so thankful that you took the time to break this down for me, and you have helped me dramatically. Makes perfect sense, and I've gone ahead and downloaded the proper fw!
I downloaded the XAC version. It says 4hrs til complete though -_-
Click to expand...
Click to collapse
You're very welcome!
Next time you can use the SamFirm tool to download MUCH faster.

Mr. Orange 645 said:
You're very welcome!
Next time you can use the SamFirm tool to download MUCH faster.
Click to expand...
Click to collapse
in 3 to 4 hours we will hear back.
all Canadian firmwares are the same and all contain multicsc lol
edit :
oh and not before odin v 3.12.x fails and have to explain to use 3.13.1
---------- Post added at 04:39 PM ---------- Previous post was at 04:24 PM ----------
Mr. Orange 645 said:
You may be right. I honestly haven't researched that part of the build number.
Edit:. It appears that's correct. I can find a list of region codes, but ironically none of them include US region codes. But that has to be the region code.
The N60U1 firmware all show a region code of UE, and the carrier branded N960U show a region code of SQ.
Thanks for the info!!
Click to expand...
Click to collapse
what i hate about samsung naming conventions is that they have at least 3 variation of them:
-device build identification (like on the oem box)
-firmware build identification
-csc build identification
and the damn country code is all diferent even if its all from the same place.

bober10113 said:
in 3 to 4 hours we will hear back.
all Canadian firmwares are the same and all contain multicsc lol
edit :
oh and not before odin v 3.12.x fails and have to explain to use 3.13.1
---------- Post added at 04:39 PM ---------- Previous post was at 04:24 PM ----------
what i hate about samsung naming conventions is that they have at least 3 variation of them:
-device build identification (like on the oem box)
-firmware build identification
-csc build identification
and the damn country code is all diferent even if its all from the same place.
Click to expand...
Click to collapse
Yeah, and it doesn't make sense. How is UE or SQ United States? Or North America? Or whatever region it represents? Hell, XX is Europe. Wouldn't EU make more sense?

Mr. Orange 645 said:
Yeah, and it doesn't make sense. How is UE or SQ United States? Or North America? Or whatever region it represents? Hell, XX is Europe. Wouldn't EU make more sense?
Click to expand...
Click to collapse
because the laymen would understand. and korea is all knowing and powerdull

bober10113 said:
in 3 to 4 hours we will hear back.
Click to expand...
Click to collapse
Heyyyy lol, so I used Odin (3.12.3) and I was expecting ti wait a long time for the fw to flash, but when I pressed start, it showed green, passed, succeeded and rebooted into the setup I had previously, all within a few seconds.
Do you (or anyone reading) know why??
I was hoping to completely reset my phone and restore to the stock FW.

imatts said:
Heyyyy lol, so I used Odin (3.12.3) and I was expecting ti wait a long time for the fw to flash, but when I pressed start, it showed green, passed, succeeded and rebooted into the setup I had previously, all within a few seconds.
Do you (or anyone reading) know why??
I was hoping to completely reset my phone and restore to the stock FW.
Click to expand...
Click to collapse
not sure what you dled but firmwares are to be unzipped and odin slots filles with:
BL
AP
CP
CSC
in your case flashing only csc.md5 should work.
you need to use odin 3.13.1
but this is besides my point. all canadian firmware contain all carriers. so you'll just end up with a reset phone full of bloat anyways.
edit:
so what carrier is your sim card from?

bober10113 said:
not sure what you dled but firmwares are to be unzipped and odin slots filles with:
BL
AP
CP
CSC
in your case flashing only csc.md5 should work.
you need to use odin 3.13.1
but this is besides my point. all canadian firmware contain all carriers. so you'll just end up with a reset phone full of bloat anyways.
edit:
so what carrier is your sim card from?
Click to expand...
Click to collapse
Yea I unzipped and placed each file accordingly. Im with Koodo (a Telus subsidiary (but its a Rogers phone so it doesnt even matter)

imatts said:
Yea I unzipped and placed each file accordingly. Im with Koodo (a Telus subsidiary (but its a Rogers phone so it doesnt even matter)
Click to expand...
Click to collapse
just flash csc.md5 NOT Home_csc.md5
try taking a screen shot of what it says on the odin screen. and also get v 3.13.1

Samsung firmwares test versions

Hello. Searching on Google I randomly found (I don't know how) this website https://fota-cloud-dn.ospserver.net/firmware/ITV/SM-N960F/version.xml . It is like a list of all RELEASED firmwares for any device and csc (in this case, my Note9 ITV). I also found https://fota-cloud-dn.ospserver.net/firmware/ITV/SM-N960F/version.test.xml , that is instead a list of test/unreleased firmwares. Like we are now with CSA7 released, but in that list there are CSA9 and CSAB already. Near every "line" there is also the "filesize", so they are actually existing packages. How can I download those firmwares? I tried to download them manually with SamFirm, but it doesn't find them (it finds only the released firmwares). Is there a way to obtain those firmwares?
NB: Sorry for my English
Thank you in advance for any reply!

obrobrio2000 said:
Hello. Searching on Google I randomly found (I don't know how) this website https://fota-cloud-dn.ospserver.net/firmware/ITV/SM-N960F/version.xml . It is like a list of all RELEASED firmwares for any device and csc (in this case, my Note9 ITV). I also found https://fota-cloud-dn.ospserver.net/firmware/ITV/SM-N960F/version.test.xml , that is instead a list of test/unreleased firmwares. Like we are now with CSA7 released, but in that list there are CSA9 and CSAB already. Near every "line" there is also the "filesize", so they are actually existing packages. How can I download those firmwares? I tried to download them manually with SamFirm, but it doesn't find them (it finds only the released firmwares). Is there a way to obtain those firmwares?
NB: Sorry for my English
Thank you in advance for any reply!
Click to expand...
Click to collapse
You can't. That site merely shows what is being tested internally at Samsung.

Question There's no published info re model variant names, & upgrade downloads not named thusly. Any thoughts?

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.