Related
** Warning For Those Using Latest Global Beta's 10.x.x **
Problem I Encountered:
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas that randomly screws up firmware for the touchscreen. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in China 9.6.7 that fixed the issue that Global 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Solution:
1.) Set you phone to Fastboot Mode (Reboot and hold down the volume-down button and power button)
2.) Connect your phone to your computer
3.) With your previously downloaded Fastboot image file of V9.6.7 China ROM, enter your choice of command
-- The command with "Flash all partitions" is recommended. ** Do Not Choose To Re-Lock Bootloader **
4.) When it finishes and reboots, your touchscreen will be functional again!
/.
boot your phone and use mouse using otg.
and try to use camera den try to vibrate...
if working... i think that is digitizer if not...
u need to flash the one partition for sensor ?
Bull****.
Sigray said:
Bull****.
Click to expand...
Click to collapse
Obviously this.
OP somehow managed to delete parts of the persist partition..or some freak accident or defective device.
I had the same experience. My device is global version, but I imported it and since I don't have un authorisation Mi store to rely on I just flashed oreo based rom with mi flash tool without knowing if ARB will trigger because I had nothing to lose. The digitizer turned on and out of curiosity I flashed 8.12.13 with the flash tool. It is working fine but for now I won't trust the updater app.
Sent from my MI 8 using XDA-Developers Legacy app
@Agimax Can confirm the issue. Faced the same problem. Followed your procedure and everything is up and running. I wonder what Xiaomi screwed up this time. Thanks a ton for the guide, was really worried for a while!
Mhm...wouldn't have thought.
Possibly something going wrong with Oreo>Pie upgrade on china devices running global roms ?
9.6.7 was the last stable release one can downgrade to on global devices and use to upgrade to pie based global beta.
I really wonder what is missing in Pie vs Oreo that the digitizer needs. I'm just worried in the future when anti-rollback is truly enabled we won't have a way to fix the issue until we find the missing/corrupted driver or file problem. Pie flashed from fastboot with all partitions should fix any issue, with files -but doesn't. That's a real problem and means they omitted something critical.
Touch Screen out of use!
Touch Screen out of use!
Same thing happened to me too. Simply after a reboot, as if the phone was initialized after the first installation (very strange) and just started, the touch no longer works.
Version Rom 8.12.13 Weekly
Agimax said:
** Warning For Those Using Latest Global Beta's 10.x.x **
Problem
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in 9.6.7 that fixed the issue that 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Click to expand...
Click to collapse
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
@Agimax
hello, I have the same problem, I was in the Xiaomi eu version 8.12.7 and all good, update to version 8.12.13 and it was all good, restart the mobile and the touch stopped working, everything you mention makes, go down to another beta version, in twrp it does not work either and just take the mouse. You can tell me how to do the process, he was in the stable global version 10.0.3.0 (oeamifh) how he made this installation, it is not clear to me the antirollback, I only have the bootloader unlocked and a backup of that version through TWRP, but I'm afraid that going back to Oreo while standing generates a brick. Please your help indicating me step by step and things to keep in mind
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Which Manual?
Which Manual? Can you post a link?
Luko69 said:
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
Click to expand...
Click to collapse
1MaxMar1 said:
Which Manual? Can you post a link?
Click to expand...
Click to collapse
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Agimax said:
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Click to expand...
Click to collapse
hello, any recommendation to rollback, according to what you say the rollback protection is not active, but I do not want to take any other surprise, I have the 8.12.13 eu! regards
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
I had also 8.12.13 xiaomi.eu, (now 8.12.20), no problem with rollback after downgrade to china 9.6.7
@Agimax
hello sorry but I'm somewhat desperate, my team is global version, I'm in Xiaomi eu 8.12.13 which version I install to recover my touch ??? The truth is I'm afraid of a brick because of that antirollback !! I hope you can help me!
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Reading is hard
Stoffl_ said:
Reading is hard
Click to expand...
Click to collapse
Sometimes i wonder why i maintain all these threads to help users......
For some reason it's especially bad with xiaomi devices. The miui forums are horrendous.
Maybe it's the user base, they are are mostly sold in Asia and India..
Agimax said:
Sometimes i wonder why i maintain all these threads to help users......
Click to expand...
Click to collapse
In my case I have read the post several times, only that I have some doubts and the truth is that I am new to the Xiaomi scene.
* I must install the Chinese version if or if or also can the global one?
* Should it be Fastboot if or if or MiFlash?
* I must install something else to avoid brick by downgrade or something from the antirollback since as you say it is not activated, it is for all devices.
I hope you understand me and before I thank you for your help, since I am desperate because I thought I would lose my cell phone.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Hi, I have a mistake with the xiaomi Redmi Note 5 I have buy for my child. I'm french but I have import it the package are close red box write global version the plug are EU version model M1803E7SG (photo 1)
When I receive it the phone are on Miui 9 Android 8. I make update on Miui 10 Android 8 no mistake all work fine.
After configure it with mi account of my child and restore Google backup & mi cloud great phone I like it. I receive update for Android 9 Pie Miui 10 I make it and when restart restore all backup but can't finish to configure it because screen freeze ??? I do to reboot to Recovery stock 3.0 and wipe data and reboot but the phone start with mi logo & powered by Android but stay and stay.
I restart it on Recovery and with mi assistant and mipc suite china beta 3.0 flash Miui 10 Android 9 Pie again I can't use miflash because the BL is lock ! I have autorization but the phone are not associed on dev settings.
After restart I configure it as a new phone and can start great but after 2min use it the screen freeze again on spring board !!!
The phone are a global version only make Ota update and don't understand why can't use it ?
Please if someone Can help me.
Thanks
That's Redmi Note 5 Pro not Redmi Note 5. Wrong forum.
Look for solutions on whyred forum
q.sadid said:
Look for solutions on whyred forum
Click to expand...
Click to collapse
Hi, mine is Redmi 5 plus and I have the same problem. I even changed the screen and it weirdly worked fine for a few days but then went back to freezing after a few minutes of use.
Just few days after installing miui 12, got this problem. The phone is stuck on a boot loop. If I pattern unlock the phone, I get a toast saying "find device stopped unexpectedly". Unfortunately, I don't have a backup. :crying:
Is there any way to save my phone? or may be get a backup?
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Dhamo200694 said:
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Click to expand...
Click to collapse
Use an Intel pc. Amd has issues with mi flash unlock too l. Run as admin. Turn off all anti virus/ firewall applications.
Having the exact same issue on my POCO F1, recently updated to MIUI 12. It was working pretty well up until 10 mins ago.
Battery went under 5% and the device went into ultra power saving mode, then restarted. Now every time I unlock the pattern, the toast pops up "Find my device..." and it goes into bootloop.
Now there isn't even a pop up, device immediately goes into bootloop.
bro, i just now facing this.. can you help me out
Well, MIUI 12 is not going good in poco F1.
If anyone who has not updated to MIUI 12, don't update the phone. Currently there are many bugs in the update
Long story short -
Some are unable to boot up the phone, some stuck in bootloop, some unable to use their passwords, some unable to set up new password, Second space not working, etc etc ...
I also updated to MIUI 12 and was unaware of the bugs.
But the device booted up and password (both fingerprint and face unlock) was working fine but I was unable to change it. Second space was working too. So I was happy that there is not much issue.
But then come the buggy part.
I started playing COD m after update and battery drained like hell 100 to 30 in 1.5 hour. I was shocked by this.
After charging I started to play again but this time (with battery issue) screen freezing happened and then happened at regular intervals. So the gaming experience on MIUI 12 was ruined.
Then I just find MIUI 9 for it and flashed it. (Ya, factory reset in this process too ?) But it is working fine now. Got fast charging module and custom thermal for gaming and it worked.
Currently no issue at all.
But I am still finding a custom kernel for poco F1 to overclock cpu and GPU (not able to find any till now).
Nearly every kernel is ment for MIUI 11 and 10 only. So I am digging deep for now to find a kernel for MIUI 9.
At last just one message - Don't update untill mi release a stable and bug free MIUI 12 version.
If MIUI 12 is working fine on your poco F1, either you are lucky or you have not encountered a bug till yet.
Without data loss, is this method come back to normal as before for poco f1 mobile?
Without data loss, is this method come back to normal as before for poco f1 mobile?
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
arulprakash2000 said:
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
Click to expand...
Click to collapse
If you don't want to loose your data, try flashing the rom using mi flash tool. But nothing can guarantee data security. You should back up your data regularly, waiting for a mishap or trusting on a single electronic device is just foolish, do make multiple copies of important data, if you want it to be secure.
I also have this problem. Updated my POCO F1 to miui 12 and it is in bootloop all the time. The bootloader is locked but I cannot unlock it now with no access to the device. How can I flash again a lower version?
If I don't mind losing the data how can I go back to previous version?
No brother, I encountered the same issues you mentioned. I stuck with MIUI logo loop after that I did a hard reset to mobile phone working condition.
Recently I updated my Realme 7 pro to android 11(through official ota). After update my phone booted and it couldn't go beyond lock screen. Lock screen blinks for a millisecond and and again this process is repeating, no key is working.
Even after reboot and deleting app data through recovery seems to be helpful.
Then I formatted my my phone, all my data lost, but finally phone started. I have to reinstall all apps and all the stuff,
Then I debloated my phone using adb,
After that I restarted my phone again same problem arrives, again I had to format my phone and again reinstall all the stuff.
If anybody found the solution please share this.
My observation with android 11
1. Seems like battery life is poor as compared to android 10.
2. Mx player keeps crashing again & again after starting.
3. No visible improvement in camera quality.
4. Still unwanted bloatware from realme and can't do anything with that.
5. App opening speed and scrolling is smooth as compared to android 10.
As now I don't find any useful thing in android 11,
So it is advised that please wait for more stable update.
That sounds not good! I am still waiting for the update. But now I am not sure if it is a good idea .....
Do you have the Global or EU version? Where do you live? I'm from Europe either the Global Version. I try to get the OTA update with a Indian VPN server.
Anyone Noticed that after 2nd android 10 update realme just degraded the widevine L1 to L3
Now I am not able to watch in hd in any app
Please help if anyone finds solution about this
And i am from india , I've updated to C.20 android 11 realme 2.0 ive done full factory reset and all sorts things like it
ramansehra said:
Recently I updated my Realme 7 pro to android 11(through official ota). After update my phone booted and it couldn't go beyond lock screen. Lock screen blinks for a millisecond and and again this process is repeating, no key is working.
Even after reboot and deleting app data through recovery seems to be helpful.
Then I formatted my my phone, all my data lost, but finally phone started. I have to reinstall all apps and all the stuff,
Then I debloated my phone using adb,
After that I restarted my phone again same problem arrives, again I had to format my phone and again reinstall all the stuff.
If anybody found the solution please share this.
My observation with android 11
1. Seems like battery life is poor as compared to android 10.
2. Mx player keeps crashing again & again after starting.
3. No visible improvement in camera quality.
4. Still unwanted bloatware from realme and can't do anything with that.
5. App opening speed and scrolling is smooth as compared to android 10.
As now I don't find any useful thing in android 11,
So it is advised that please wait for more stable update.
Click to expand...
Click to collapse
Same thing happened to me! I had to reset and lost valuable data
Now I can't debloat, because the same thing happens - lock screen keeps blinking, no way to do anything.
If someone has a safe to uninstall list on Android 11, please share
I have updated my Realme 7 Pro (Europe) just a few days ago. Reading all this complains made me sceptical installing the new update but believe me guys that i am glad and very happy with this new android 11 update. No issues on booting, no heating problems, very smooth UI, great battery life ( 8-10 hours of SOT, with 20-25 % screen light). I read on telegram that booting issues appear on Realme 7 Pro when users debloat the initial apps via ADB (weather app) and then make the android 11 update.
ramansehra said:
Recently I updated my Realme 7 pro to android 11(through official ota). After update my phone booted and it couldn't go beyond lock screen. Lock screen blinks for a millisecond and and again this process is repeating, no key is working.
Even after reboot and deleting app data through recovery seems to be helpful.
Then I formatted my my phone, all my data lost, but finally phone started. I have to reinstall all apps and all the stuff,
Then I debloated my phone using adb,
After that I restarted my phone again same problem arrives, again I had to format my phone and again reinstall all the stuff.
If anybody found the solution please share this.
My observation with android 11
1. Seems like battery life is poor as compared to android 10.
2. Mx player keeps crashing again & again after starting.
3. No visible improvement in camera quality.
4. Still unwanted bloatware from realme and can't do anything with that.
5. App opening speed and scrolling is smooth as compared to android 10.
As now I don't find any useful thing in android 11,
So it is advised that please wait for more stable update.
Click to expand...
Click to collapse
did u reset phone after update?
After waiting many months for an update for my OnePlus Nord 2 Europe (EUEX), I managed to easily get the Android 12 update. Shortly, I installed over my EU Android 11 (with A.21 version and June patch security) the Indian firmware C.09 with September patch.
Phone is not rooted, bootloader is locked and has the orriginal recovery.
So in OxygenUpdater I selected India and full rom, instead of EU. After download, I shut down the phone, then by pressing Power and Volume down I entered recovery. I selected the desired language, then Local install and the firmware which is a file with long alphanumeric name. The full update takes no more than 5 minutes.
No data is deleted, the apps and the settings are there.
Greetings and credits to @asotmike who helped me.
Interface is buttery smooth, no lags, no bugs after 6 hours of playing with the phone. All functions work ok, Vowifi, Volte and 5g working fine in Romania.
For now, I don't know if there is an easy way to return to Europe version, without using MSM tools and losing data, so please everyone think well if you take the risk of making this movement.
Can you enter fastbootd and BROM mode?
Updating to EU ROM will be posible when / if OP releases full ROM > C.09 for DN2103.
Adb reboot fastboot works, it enters fastboot mode where it shows Format data, Reboot, Power off. In brom mode how can I enter, to test later? And I think you are right about moving back to Eu, only when a Eu build C.09 or newer is released
everything ok for me also. thanks to OP for this, finally we got android 12.
Thank you from Romania also ! A12 is something else ... It's OK for now .
Glad you like it guys! Hope to see many updates now for our great phone.
ruh01 said:
Adb reboot fastboot works, it enters fastboot mode where it shows Format data, Reboot, Power off. In brom mode how can I enter, to test later? And I think you are right about moving back to Eu, only when a Eu build C.09 or newer is released
Click to expand...
Click to collapse
You confirm that fastbootd is not available anymore. The phone boots to recovery.
For testing BROM mode you need mtk client. To enter you need to switch off completely the phone, connect the USB cable to the PC only. Then connect this cable to the phone and immediately press and hold all 3 buttons ( vol+, vol-, power ). The device screen should remain completely black and mtk client should detect your phone and connect it. Once detected you can release all the buttons.
I suppose, as per other reports that BROM is disabled too, so no more easy custom ROM installation or servicing.
Thank you.
For recovery and fastboot there is a difference, but small.
If I use adb reboot recovery I get to select language and after there is a menu named Recovery with options Fromat data, Reboot device and Power off.
If I use adb reboot fastboot, I select language and after there is a menu named Fastboot but with the same options as in case of recovery.
I cannot test Brom because I have downloaded several versions of MTK client but none of them even starts on my computer...
ruh01 said:
For recovery and fastboot there is a difference, but small.
If I use adb reboot recovery I get to select language and after there is a menu named Recovery with options Fromat data, Reboot device and Power off.
If I use adb reboot fastboot, I select language and after there is a menu named Fastboot but with the same options as in case of recovery.
I cannot test Brom because I have downloaded several versions of MTK client but none of them even starts on my computer...
Click to expand...
Click to collapse
Yes, install mtk client involves installing drivers, python, etc. It's a bit complicated. Unfortunately without fastbootd and BROM, one cannot customize the phone. If is ok with stock no matters.
Cheers.
I am very happy with this non-orriginal version. I found no problems yet, in 1 and half day. Should OnePlus start pouring with updates for EU, maybe I will return with a newer variant of DN2103. Else, adieu. Everything works fine, all apps, network bands work fine. Fast, smooth, no bugs, same great camera and performante, no sound problem. I will study further and play with it.
Unfortunately I found some small insignificant bugs like annoying slow connection to WiFi 6 , A11 was quite fast . Ambient display still don't work , picking wallpaper from Settings is blocked (I can set wallpaper only from particular 3.rd launcher apk . Percent battery is randomly shown despite it isn't set . Battery drain is bigger then A11 . Browsing is also slower . Fingerprint gave several errors and send me to PIN even I re-enroll new fingerprint , animation are ugly . Proximity sensor has also rare errors . More then that there are some stupid bloatware (maybe for Indian Market ). I didn't use for now Bluetooth , Android Auto , Portrait camera , and other complaints of indians users ... But overall A12 is working fine although I expect further EU version if it comes anymore !
Untill we have a proper EU version and a good update frequency for it, I am more than happy to stay with this version. We'll see if this happens, ever...
Yeah , right ... Am I pleased with A12 ? NO ! Should I go back to A11 ? NO... hahahahaha
thanks. it works also for me. Model name changed to DN2101 XD
tbh, i didn't find any bugs on IN version. 5G is working fine (Greece), wifi is the same fast as A11 (less than 1 sec.), bluetooth also ok. i can't compare the battery drain because i own the phone for less than a month but i think it's the same as before. if they decide to give EU version and update it regurarly maybe I will switch again, but I don't mind staying with the IN that updates every month. cheers!
greg10 said:
tbh, i didn't find any bugs on IN version. 5G is working fine (Greece), wifi is the same fast as A11 (less than 1 sec.), bluetooth also ok. i can't compare the battery drain because i own the phone for less than a month but i think it's the same as before. if they decide to give EU version and update it regurarly maybe I will switch again, but I don't mind staying with the IN that updates every month. cheers!
Click to expand...
Click to collapse
They release primary for DN2101. When fixed the main bugs, OP made it available for the DN2103. So we can expect European releases will be more stables, but delayed...
roldev said:
They release primary for DN2101. When fixed the main bugs, OP made it available for the DN2103. So we can expect European releases will be more stables, but delayed...
Click to expand...
Click to collapse
the latest version they released for EU was C.01 and we weren't able to get the update, so I'm not really sure for that
greg10 said:
the latest version they released for EU was C.01 and we weren't able to get the update, so I'm not really sure for that
Click to expand...
Click to collapse
They have weird schedule. C.01 is available for Spain since the first day released. Through system update or oxygen updater.
roldev said:
They have weird schedule. C.01 is available for Spain since the first day released. Through system update or oxygen updater.
Click to expand...
Click to collapse
HI I have EU and version is DN2103_11_ cC08 got it about 2 weeks ago. Before update I had C.01
jis251 said:
HI I have EU and version is DN2103_11_ cC08 got it about 2 weeks ago. Before update I had C.01
Click to expand...
Click to collapse
Thanks for confirming. There are various regions which got the C.08. My oxygen updater still shows C.01 as latest available.