Database Develop

[SOLVED] Pie october update failed

I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...

Same problem and I didn't find any solution yet.

Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli

It worked for me mate! Thank you

k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.

Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...

jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...

proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?

Worked for me too, thanks!

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader

wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.

Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse

I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.

whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...

Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse

I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.

Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse

whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.

Can't update to WW1908 from WW1907

On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY

Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908

stealthj said:
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
Click to expand...
Click to collapse
Let me download it again. Hope it works. If this does work, I will feel a lot better about updating my awesome phone in the future. Coming from Samsung on AT&T hopefully ASUS keeps the updates fairly regular.

Nope, still not working. Oh well, guess I can wait for the raw version.
But if anyone has any ideas on what I am missing, please chime in.

jkeener88 said:
On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Click to expand...
Click to collapse
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good

xxBrun0xx said:
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
Click to expand...
Click to collapse
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.

jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12

jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.

skromnia said:
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
Click to expand...
Click to collapse
Thanks, ya learning a lot on this phone. Just got figure it all out without bricking my ROG!

xxBrun0xx said:
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
Click to expand...
Click to collapse
Thank you so much for pointing me in the right decision, and also although I don't see that many Subaru vehicles in Houston, I plan on getting one this year or maybe next year. Thanks again, up to 1908 now. :good:

Chinese 8gb Tencent q
I'm on 1906 ww. I understand this phone needs a manual flash each time, do I need to flash with every update using raw files and will this also wipe the phone so every update means a wipe?
Can I root, install twrp and simply update the firmware no issue or is it bs?

How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update

viper98 said:
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
Click to expand...
Click to collapse
i just update to to latest one
u need twrp
put twrp and magisk and the update on root of ur device
flash twrp it will crash first time the next restart will work without any problem
flash and select the latest ota update that u downloaded from asus it take some time
then flash twrp again then flash magisk after all done reboot
work for me no problem

Question Internal Storage Encrypted

I need some help, I have Mi 11 Ultra CN version, I unlocked BL and install the Global Rom using fast boot, I enjoyed it, but battery seems to suck.
I installed MIUI EU 12.5.4 and now that I'm trying to update it to EU 12.5.7.0 within the phone, it tells me my internal memory is encrypted. How can i install the update or decrypt my internal memory. It does not allow me to install the update... any help will be appreciated it..

Mr_creeper_98 said:
I need some help, I have Mi 11 Ultra CN version, I unlocked BL and install the Global Rom using fast boot, I enjoyed it, but battery seems to suck.
I installed MIUI EU 12.5.4 and now that I'm trying to update it to EU 12.5.7.0 within the phone, it tells me my internal memory is encrypted. How can i install the update or decrypt my internal memory. It does not allow me to install the update... any help will be appreciated it..
Click to expand...
Click to collapse
Remove lock screen security

NOSS8 said:
Remove lock screen security
Click to expand...
Click to collapse
I don't have a password, or lock pattern for lock screen..

Mr_creeper_98 said:
I don't have a password, or lock pattern for lock screen..
Click to expand...
Click to collapse
You can try with Mi flash (dont relock bootloader)

MIUI EU 12.5.4 not EEA but CN version

Set a lock screen lock, then go to twrp and use it to unlock and decrypt the storage

i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all

Mr_creeper_98 said:
i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all
Click to expand...
Click to collapse
There is no downsize. You are only replacing stock recovery with a different version. It has no affect on your phone, it's and your own data. It just makes it easier to flash custom or even returning to stock if required as well as other tools offered in the TWRP package.

Mr_creeper_98 said:
i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all
Click to expand...
Click to collapse
can you tell me how you did that?i have the same problem with my mi 11 ultra.CN version ,put the global version on it 12.5.4.0 and cant update to 12.5.7.0 because encrypted internal storage.
im not well known with TWRP.

Try what I wrote in post 3, https://forum.xda-developers.com/t/internal-storage-encrypted.4289325/post-85151561

I don't know what I do wrong but I installed twrp but it said that my phone is not rooted

sheephurther said:
I don't know what I do wrong but I installed twrp but it said that my phone is not rooted
Click to expand...
Click to collapse
Give me a couple of hours until I get home and I'll show you how I did it.. I did not root my phone BTW

@sheephurther I used this Xiaomi ADB/Fastboot to install TWRP
https://github.com/Szaki/XiaomiADBFastbootTools/releases/tag/7.0.3
Hope this will help you..
Make sure phone is in ADB Debugging mode.

Thanks.i gonna try later today.i let you know if it worked.

sheephurther said:
I don't know what I do wrong but I installed twrp but it said that my phone is not rooted
Click to expand...
Click to collapse
Installing twrp doesn't install root. It just replaces the system recovery. If you really want root, use Magisk but I've not found any reason to root my phone for ages.

I tried today but it doesn't work.
To bad!!I'll try it later on.

sheephurther said:
I tried today but it doesn't work.
To bad!!I'll try it later on.
Click to expand...
Click to collapse
Did you try setting a lock screen pin, pattern or pw and then using it to decrypt in TWRP? I'm using 3.5.1 twrp version fine.

sheephurther said:
can you tell me how you did that?i have the same problem with my mi 11 ultra.CN version ,put the global version on it 12.5.4.0 and cant update to 12.5.7.0 because encrypted internal storage.
im not well known with TWRP.
Click to expand...
Click to collapse
Change your password to 1234 and try it again
When your get asked to decrypt enter 1234 and press the ok bottom on the bottom right

Is there a film on YouTube that exactly tells how to install Twrp on mi 11 ultra?I tried several but it does not work.how difficult can it be??or maybe I am Tu stupid

I sold a phone yesterday to somebody, doing the full wipe before that. It was on the latest weekly Xiaomi.eu. Now it has this issue. Is it possible that it is the same thing?

Question Is there a way to force/download OTA updates?

Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!

hgoor said:
Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!
Click to expand...
Click to collapse
Try this
https://c.mi.com/oc/miuidownload/detail?guide=1
https://c.mi.com//miuidownload/detail?device=1900395

.

NOSS8 said:
Try this
https://c.mi.com/oc/miuidownload/detail?guide=1
https://c.mi.com//miuidownload/detail?device=1900395
Click to expand...
Click to collapse
Hey thanks for taking the time to answer my question..
Your first link brings me to a blank page with only an add for MIUI community app.
Your second link shows a download page which doesn't show a version, only says "global" and actually also say "modified copy" in Chinese.
So yeah, I'm not going to just risk that if you don't mind...

hgoor said:
Hey thanks for taking the time to answer my question..
Your first link brings me to a blank page with only an add for MIUI community app.
Your second link shows a download page which doesn't show a version, only says "global" and actually also say "modified copy" in Chinese.
So yeah, I'm not going to just risk that if you don't mind...
Click to expand...
Click to collapse
Links are clear.
You can upgrade your phone by Local Update method without unlocking your phone. The method suits for the situations listed below for sure: Update to Global Stable ROM from Global Stable ROM, Update to Global Beta ROM from Global Beta ROM, Update to Global Beta ROM from Global Stable ROM and vice versa. If you encounter the issue that the reboot page keep loading for a long time after flashing, you can choose to wipe all data via entering Recovery Mode. You can turn off your device and then hold both Volume+ button and Power button at the same time to enter Recovery Mode.
STEP 1​Download the latest MIUI ROM file Click here to download
There is no need to do it again if you’ve already downloaded the latest ROM file.
STEP 2​Connect your device to the Windows PC/laptop via a micro USB cable, and copy the ROM file downloaded in Step 1 into the folder ‘downloaded_rom’ in the internal storage of your device.
STEP 3​Launch ‘Settings’ app on your device, select ‘About phone’, click ‘System update’, then press ‘three dots’ icon at the top-right corner, and select ‘choose update package’ to enter. Choose the ROM file you’ve put in ‘downloaded_rom’ in Step 2.
View Image
STEP 4​After choosing the right ROM file, your device will begin upgrading. Your device should automatically boot to the new version when the update is completed.

Go to system update->tap on the main icon 5/6 times,this will unlock hidden settings->now download manually from trusted websites like mifirm the RECOVERY version of YOUR rom. ->go then to update again and select on the three dots at the up right "choose update package"

xNAPx said:
Go to system update->tap on the main icon 5/6 times,this will unlock hidden settings->now download manually from trusted websites like mifirm the RECOVERY version of YOUR rom. ->go then to update again and select on the three dots at the up right "choose update package"
Click to expand...
Click to collapse
Thanks! Will this procedure wipe my phone, or update it like regular OTA?

regular OTA.
but after an update, resetting avoids bugs

hgoor said:
Thanks! Will this procedure wipe my phone, or update it like regular OTA?
Click to expand...
Click to collapse
Regular OTA

xNAPx said:
Regular OTA
Click to expand...
Click to collapse
Ok tried it, got the right version, but says it can't be verified so no go on the updating..

NOSS8 said:
regular OTA.
but after an update, resetting avoids bugs
Click to expand...
Click to collapse
Right i understand. However downloading the right version didn't work; got error that it could not be verified..
hgoor said:
Ok tried it, got the right version, but says it can't be verified so no go on the updating..
Click to expand...
Click to collapse
Nevermind downloaded again, now verified..
Attempting update!

hgoor said:
Right i understand. However downloading the right version didn't work; got error that it could not be verified..
Nevermind downloaded again, now verified..
Attempting update!
Click to expand...
Click to collapse
If nothing works, try changing the region: belgium.

There are some fix for errors like that,check it out

This video shows a way how to do it:
Can't confirm if this is the best/official method, but it seems easy.

Ok guys thanks! I was able to update without issues.
I was hoping it would fix a bug I face with setting custom ringtones, but it didn't.. very annoying..
But thanks anyway! I'm on latest stable now..

hgoor said:
Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!
Click to expand...
Click to collapse
https://xiaomirom.com/en/series/star/ updated daily

Question MIUI 14 - settings reset after reboot

Hello, anyone experience reset of settings like, carrier settings, battery optimization etc, after reboot of the device? MIUI Global 14.0.3.0 (TKBEUXM)

Mh, seems a bug of the new release.
Have you tried to backup and reflash the stock ROM?

zSyntex said:
Mh, seems a bug of the new release.
Have you tried to backup and reflash the stock ROM?
Click to expand...
Click to collapse
Hi, I've done factory reset after update, still same issue.

pYdzin said:
Hi, I've done factory reset after update, still same issue.
Click to expand...
Click to collapse
Looks like a new fw bug so.
Wait for an update, because I think that the previous release wasn't affected by this, was it?

I am not 100% sure, but I think 14.0.2 had the same issue

pYdzin said:
I am not 100% sure, but I think 14.0.2 had the same issue
Click to expand...
Click to collapse
Could you please explain exactly how the carrier settings reset? I will be testing 14.0.3 today and I can check for the issue.

Maybe I didn't describe it properly. My mobile network provider requires to set access points for internet and MMS manually when sim card inserted in new phone. Now everytime I do reboot, I need to maintain them again, because it resets those settings, ridiculous.

pYdzin said:
Maybe I didn't describe it properly. My mobile network provider requires to set access points for internet and MMS manually when sim card inserted in new phone. Now everytime I do reboot, I need to maintain them again, because it resets those settings, ridiculous.
Click to expand...
Click to collapse
You mentioned that you made a factory reset but the issue persists.
I clean flashed through fastboot and I can confirm I did NOT face this issue. I have to set my APN manually as well and the battery optimization but both of those stayed the same after the reboot. Version 14.0.3

Unknown.Guy said:
You mentioned that you made a factory reset but the issue persists.
I clean flashed through fastboot and I can confirm I did NOT face this issue. I have to set my APN manually as well and the battery optimization but both of those stayed the same after the reboot. Version 14.0.3
Click to expand...
Click to collapse
Good for you, but it should not work like that. We should update system by OTA and everything should be ok. When I did factory reset it just wiped data and stay with 14.0.2. I didn't flash ROM by Fastboot

pYdzin said:
Good for you, but it should not work like that. We should update system by OTA and everything should be ok. When I did factory reset it just wiped data and stay with 14.0.2. I didn't flash ROM by Fastboot
Click to expand...
Click to collapse
Thanks. I think you should join the Global Telegram group and share the issue there so others can report it and Xiaomi can workout the issue.

https://telegramchannels.me/channels/xiaomi
Did you mean this one or there is another one? I am not that familiar with Telegram

The following:
Mi 11(Venus)-Global Community
t.me

Unknown.Guy said:
The following:
Mi 11(Venus)-Global Community
t.me
Click to expand...
Click to collapse
Thanks

pYdzin said:
Good for you, but it should not work like that. We should update system by OTA and everything should be ok. When I did factory reset it just wiped data and stay with 14.0.2. I didn't flash ROM by Fastboot
Click to expand...
Click to collapse
Fastboot wipes all the data, yes?

pYdzin said:
Fastboot wipes all the data, yes?
Click to expand...
Click to collapse
It depends. You can choose not to wipe. But I usually always wipe completely for the best experience.

Unknown.Guy said:
It depends. You can choose not to wipe. But I usually always wipe completely for the best experience.
Click to expand...
Click to collapse
Of course bootloader must be unlocked?

pYdzin said:
Of course bootloader must be unlocked?
Click to expand...
Click to collapse
It depends whether your device is China version or Global version by default. Which one is yours?

Unknown.Guy said:
It depends whether your device is China version or Global version by default. Which one is yours?
Click to expand...
Click to collapse
I flashed RKBEUVF (operator version) to SKBEUXM some time ago MIUI 13 and I needed bootloader unlocked, what about now? This were never Chinese version.

pYdzin said:
I flashed RKBEUVF (operator version) to SKBEUXM some time ago MIUI 13 and I needed bootloader unlocked, what about now? This were never Chinese version.
Click to expand...
Click to collapse
So if you didn't lock your bootloader after flashing the new version, that means the bootloader is still unlocked. And you could go ahead with clean flashing EEA fastboot.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com

Unknown.Guy said:
So if you didn't lock your bootloader after flashing the new version, that means the bootloader is still unlocked. And you could go ahead with clean flashing EEA fastboot.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
I flashed and locked bootloader