I've bought this phone only few days ago. Connected to wifi I started to install the updates included the OTA of Android Pie. After doing that my phone started to show a important wifi error. It could connect to my hotspot wifi (made with my second phone) but not to home wifi and work wifi. After trying to reset wifi settings, wipe data,... I decided to try to go back to Oreo using MIflashtool and the last Android One Rom available on miui english site.
I unlocked bootloader and put the phone in edl mode. I flashed the rom with clear all option active.
Now the phone, if it is tried to be power on, show the "Android One" logo and then it loop reboot.
I can go to fastboot, edl, can install twrp etc...
What should I do?
Really Thanks
Sungfive said:
I've bought this phone only few days ago. Connected to wifi I started to install the updates included the OTA of Android Pie. After doing that my phone started to show a important wifi error. It could connect to my hotspot wifi (made with my second phone) but not to home wifi and work wifi. After trying to reset wifi settings, wipe data,... I decided to try to go back to Oreo using MIflashtool and the last Android One Rom available on miui english site.
I unlocked bootloader and put the phone in edl mode. I flashed the rom with clear all option active.
Now the phone, if it is tried to be power on, show the "Android One" logo and then it loop reboot.
I can go to fastboot, edl, can install twrp etc...
What should I do?
Really Thanks
Click to expand...
Click to collapse
Hello,
Try flash stock rom but in fastboot mode using MiFlash
Pierre
Drop a thanks if I help you
Pierre_C said:
Hello,
Try flash stock rom but in fastboot mode using MiFlash
Pierre
Drop a thanks if I help you
Click to expand...
Click to collapse
Already tried both in edl mode and fastboot
No way
Sungfive said:
Already tried both in edl mode and fastboot
No way
Click to expand...
Click to collapse
Do fastboot getvar all and send me the output please
Pierre
Pierre_C said:
Do fastboot getvar all and send me the output please
Pierre
Click to expand...
Click to collapse
Thanks for the help. Probably Xiaomi did something "wrong" with the Android Pie Update. I had to wait till the fastboot .tgz file of Android Pie and flash it trough Miflash. Now it rebooted correctly.
Thanks anyway for your help
Sungfive said:
I've bought this phone only few days ago. Connected to wifi I started to install the updates included the OTA of Android Pie. After doing that my phone started to show a important wifi error. It could connect to my hotspot wifi (made with my second phone) but not to home wifi and work wifi. After trying to reset wifi settings, wipe data,... I decided to try to go back to Oreo using MIflashtool and the last Android One Rom available on miui english site.
I unlocked bootloader and put the phone in edl mode. I flashed the rom with clear all option active.
Now the phone, if it is tried to be power on, show the "Android One" logo and then it loop reboot.
I can go to fastboot, edl, can install twrp etc...
What should I do?
Really Thanks
Click to expand...
Click to collapse
Extract rom folder and flash with "64-bit" mi flash in EDL mode
https://yadi.sk/d/cel5Nm2sE1OpMg
This link is 64 bit version of mi flash
I have a bricked Redmi Note 5 Pro. Stock firmware, locked bootloader, did literally nothing that would cause this. Just updated firmware (it happened few years ago, just now decided to try and repair it), and after update It's stuck in Mi-Recovery 3.0, with options only for "Reboot", "Wipe Data" and "Connect with MIAssistant", with red text at the bottom "This MIUI version can't be installed on this device" (see photo). Tried everything form this menu, nothing solves the problem. I can boot into fastboot but can't use it as the bootloader is locked and debugging is off. I can go into EDL mode but can't flash as I need to log in into Mi Account, and my sister (this phone was hers) forgot the password and even the account which was connected to this device. I was looking for MiFlash that bypasses authorization but can't find any that is not marked as malware (anyone knows of any that is safe?). At was past the warranty and I've tried to ask few phone-repair shops but the said that is unrepairable.
Any ideas what I can check or try next to solve this problem?
BTW. Does anyone knows why all of this happened? As I already said, never did anything with OS, only updated it which caused brick. My only idea is, as this phone was bought not from official store, that it might be a phone that was bought cheaper in china, then flashed with modified global OS and after update it was replaced with official global OS which bricked the phone. No idea if something like this is possible.
Edit [Sep 19, 2021]: I got somewhere. Used Firehose file to flash whyred global image without authenitcation. Got into system. I can at least go into fastboot and it's detected correctly in windows. Now I'm trying to get root, flash TWRP and any non-stock OS. Couldn't flash directly via fastboot because of anti-rollback check. Tried to do "fastboot boot twrp_rn5pro.img" which resulted in FAIL in console (status read failed - too many links) and "The system has been destroyed - click the power button to shutdown".
Edit2 [Sep 19, 2021]: Looks like my bootloader is still locked and that's why I can't flash custom recovery. But when I look in the phone settings it says that my phone is already unlocked. Checking in fastboot via PC says otherwise. Enabled OEM unlocking, but fastboot still says "FAILED (remote: Token Verify Failed, Reboot the device". Can't unlock it using MiUnlock cause they say that I need to set my account as available to unlock in unlock status on my device, but I can't do it as my device says that it's already unlocked.
Edit3 [Sep 20, 2021]: I've tried other tool: XiaoMiTool V2 (by Francesco Tescari). As the option "My device works normally I want to mod it" didn't work I chose "My device is bricked I want to unbrick it". Selected option without unlocking bootloader (wouldn't work). And it actually auto-detected that it's chinese phone and flashed chinese OS (MIUI 10.3 Stable). At the boot I got a prompt that this device is locked and I need to log into my Mi account (the one I logged in in the last ROM - from first Edit), after logging in it let me go through setup (luckily there was English). But phone still says that it's unlocked while it's still locked in fastboot. So in the end it didn't got me anywhere, but at least I know that orginally it was a chinese phone.
Edit4 [Sep 20, 2021]: Finally solved the problem! Used this tutorial. Did everything like shown on video and at the end I have MIUI 12 with unlocked bootloader (this time it's actually unlocked - checked with fastboot). Managed to flash TWRP using dummy.img and flashing to recovery. Couldn't boot from img, but vol+ + power did the job. With working recovery I can do everything else I wanted to do.
I had the same issue, which I also managed to fix. I thought I'd share what I did here.
My phone was bricked with access to MIUI recovery and Fastboot. My phone was locked, however my phone was not linked to my Mi account, and so I couldn't unlock it using the Mi Unlock tool. The only way to get into EDL mode was via the testpoint method. It's not as scary as people may think.
Many of the YouTube videos on testpoint show that you have to touch the two terminals while pushing the cable into the phone. Several times I was able to activate EDL mode without doing both at the same time - i.e. I could just connect the cable and touch the two terminals (I used a paper clip) and the phone would enter EDL mode. I think it might have had something to do with me pressing the power button. In my case, I had to have the battery disconnected from the circuit to get into EDL mode.
I used the Xiaomi Flash tool. Always remember to select not to relock the bootloader. I think it's stupid that relocking is the default option and that the radio buttons are at the bottom of the program and sometimes not visible on a laptop. That's how I got into this mess in the first place!
One of the things that I think causes the "MIUI version" problem is attempting to install the incorrect stock ROM. The phones may be fussy about which stock ROM they will accept. In my case, I thought the phone was a global version, then worked out that it was probably a Chinese version.
I replaced the firehose files in all the ROMs I attempted flashing with the ones supplied on XDA. The Xiaomi Flash tool reported success several times, but when starting up the phone it would go into recovery with the "MIUI version" message. I tried about six different MIUI ROMs with the testpoint method, both global and Chinese, before stumbling on the one that worked (after replacing the firehose files): whyred_images_V11.0.2.0.PEICNXM_20191023.0000.00_9.0_cn
When I got back into MIUI, I linked the phone to my MI account and then attempted flashing the latest LineageOS (which was what I was trying to do in the first place), using the Lineage recovery. The phone wasn't accepting the Lineage recovery, so I flashed OrangeFox-R11.0-Stable-whyred. I had to boot to Orangefox in order to flash it. You copy the Orangefox zip file to your phone using your computer when you have MIUI up and running, then you enter Fastboot and run the following command from your computer:
fastboot boot recovery.img
From Orangefox, you then select the Orangefox zip file on your phone and swipe to install.
Once that was done, I rebooted to recovery and did a wipe of the phone. It wasn't enough for me to wipe Dalvik/ ART Cache and Cache (as recommended), I had to also wipe System, Vendor and Data. (I tried just the first two and the LOS installation was corrupt, even though it was reported as being successful.) I then copied LOS to a micro SD card, inserted it into the phone and mounted it, before flashing LOS by navigating to the zip file on the SD card, selecting it and selecting wipe to install.
Finally success!
I think the key with the testpoint method is to keep trying ROMs until you stumble on the one that works. If the Xiaomi Flash tool reports success, I think it means you are doing something right. I also wonder if a lot of people who have the "MIUI version" issue have a phone with the Chinese ROM and don't realise it.
Hope this helped someone!
by any chances how do you unlock bootloader if you just bypass the mi account?
yoshukii19 said:
by any chances how do you unlock bootloader if you just bypass the mi account?
Click to expand...
Click to collapse
No hacking ... Why did you bypass mi account???
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
the reason is I got my phone Redmi Note 5 Pro on fb marketplace by swapping my old phone, when I'm using it there's no mi account logged in on my phone then I tried to install the latest MIUI 12 by flashing it on MiFlash but I didn't notice that I didn't change the setting on clean all so it locked my bootloader, after I manage to fix the issue about my phone because it doesn't open and it only boot on recovery with a message "This MIUI...." and make it boot by flashing cn official rom, it says that my phone is locked and I need to logged in the old mi account, I already ask the previous owner but he said he doesn't have an access on that account, even the number and email are already lost
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Aurora333 said:
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Click to expand...
Click to collapse
Why did you quote me?!?
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
You must have the firmware requested by the OP, flashed it if necessary.
See this rom below where everything is explained.
https://forum.xda-developers.com/t/rom-13-official-pixelos-aosp-unified-11-09-2022.4237791/
Other TWRP/OF.
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/willow/
Regrettably, my telephone is now hard-bricked. Recovery and Fastboot modes also not possible, so back to stock-ROM is no longer possible either. Only a flashing screen, and - when trying to enter fastboot mode, only short showings of the word fastboot, but no response in MiFlash. I think that a new phone is unavoidable.
Meanwhile, I've tried to enter EDL mode. Troed various fastboot commands, but no response from the telefone. Ultimately, I've tried to open the backcover (in order to reach the so-called "test points"), but that's easier said than done.
Website
is pretty clear, I know where to find those test points, but I'm lacking a 'heat gun', demonstarted in the youtube film. I tried it with a hairdryer, but that proved ineffective, moreover, the hairdryer stopped working (overheating?). Still need to check a possible fuse in the hardryer. Anyway, I'm awaiting a Redmi Note 11...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
But what went wrong in the first place?
The flashing instructions quoted
Flashing Instructions
Clean flash (coming from a different ROM):
• Flash recovery (links above)
• Download ROM from the link above
• Download Magisk v23.0 or newer (optionally)
• Reboot to recovery
• Format data (if encrypted)
• Wipe system, vendor, cache, dalvik, data
• Flash latest android 11 global stable firmware (link above)
• Flash ROM zip
• Reboot and voila!
It mentions "flash recovery". The only method to install TWRP that I know, is through fastboot commands (fastboot flash recovery twrp.img, after having renamed the latest twrp image file), and then "fastboot reboot" while keeping Power + Volume Up pressed.
Prior to this, I had placed the firmware-, ROM- and Magisk-files on the phone.
After installing TWRP and Magisk, I wiped cache and Dalvik.
Then, when tried to flash the ROM, apparently that was wiped too. I think that it would have been better to reboot the phone after installation of TWRP and Magisk, then transfer the firmware and rom-files to the phone, and then boot into recovery again.
Anyway, that was not what I did...
Right after installation of TWRP and Magisk, having seen that the files to be flashed, were no longer there, I tried to install the firmware- and ROM-files with 'adb sideload' commands from TWRP. The flashing process seemd to go well, but booting to system proved disastrous...
A 'lesson learned' - at least for me: do not proceed if you - for some reason - can't follow the instructions. but break off, so that you can still reflash the stock-rom!
Sometimes, flashing the firmware with the Twrp does not work and you have to flash the complete rom with Miflash.
For EDL mode you will not have the necessary authorization.
See my PM.
gjongbloed said:
But what went erong in the first place?
Click to expand...
Click to collapse
1st
2nd
what brick your phone is relocking the bootloader
never do that on a redmi note 8 !
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
gjongbloed said:
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
Click to expand...
Click to collapse
Redmi note 8t(Willow).
Anyway, even if you had done it, it wouldn't have changed anything,except that you would have relocked the bootloader, since this model is intended for the global market with roms, Global, EEA, Russian, no CN roms.
Situation at present (4-11-2022): I have succeeded in opening the telephone in order to make the 'test points' approachable and to disconnect the battery. In the 'device manager', I've seen 'Qualcom' appearing on one of the com-ports. To continue, I now have to await a 24 hours break after too many times of opening my Mi-account during earlier attempts of flashing with the MiFlash tool .
.....
Well, 24 hours later, I've come to the conclusion that my brick definitively remains a brick. Tried again and again, but each time received an error "Cannot receive hello packet. MiFlash is trying to reset status.". And that's it...
Meanwhile, I had the impression that I might have better results with the Qualcomm tool QPST. The telephone - in EDL mode - was observed in QPST Configuration all right, but the flashing with QFIL failed with a consistent error: Unable to read packet header.
I've seen many reported occurrences of this error in various XDA fora, but nowhere a conclusive remedy. I'm out of options now...
Now, I get the information that the file that I want to flash, is too large. If only there could be a smaller file, only to restore the part of the os, through which to activate the fastboot and recoverymodes...
Well, after many tries, searching for solutions for the various Sahara fails that I encountered while using QFIL, I found a solution that really worked:
[GUIDE] How to unbrick RN8 (won't boot only backlight turns on for a second) using EDL
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8 original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/ many thanks to dxD7 who provided...
forum.xda-developers.com
I could use the patched firehose file also on an older Global EEA version of the stock-ROM, and then everything worked fine... It took a while, updating the phone to the latest version, but that doesn't matter...
Well... the phone is working again with MIUI Global 12.5.5.0 (RCXEUXM).
Working, but... both IMEI's are null, therefore SIM cards are no longer recognized, which means that I can't use the dial function and can't use a mobile network. WiFi is working.
Moreover, the bootloader is locked again, but I can't unlock it with MiFlash Unlock, because this procedure requires connection via a mobile network. And without an unlocked bootloader, any possibility to root the phone, flash a repaired qcn file (with proper IMEI's), try out custom ROMs or whatever, is blocked...
Any option left? (Fastboot and EDL mode still possible).
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
gjongbloed said:
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
Click to expand...
Click to collapse
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Cristina.D.M said:
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Click to expand...
Click to collapse
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
gjongbloed said:
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
Click to expand...
Click to collapse
WoW, It is boomshell, Now I do know what is "One is never too old to learn".
Thanks ever so much for your reply.
Hi all,
I hope someone will be able to guide me as how to recover from this.
So today I tried flashing my POCO F3 with MIUI 14 (xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13) from the stock version MIUI 12.
I first successfuly unlocked the bootloader using MiUnlock. I then unlocked the developer options , usb unbugging etc. again on the fresh phone.
I also had USB / ADB and fastloader drivers installed.
I downloaded xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13 , phone was already in fastboot and connected to the computer so run 'windows fastboot first install with data format' as an administrator which opened the cmd , after agreeing it started flashing the first few files successfully but when it gets to " Sending 'cmnlib64_ab' (504 KB) " the process just stopped there and it has been like this for around 30 mins - no error ...simply stuck on this step .....
I am not sure on what to do now to avoid bricking my phone, should I leave it connected ? Disconnect it and try flashing it again ? Download an older version of Xiaomi.Eu ROM (e.g MIUI 13 ) ?
Leave it connected for about 1 hour or so until you get success or error confirmation. If failed just reboot to system. If system failed to show up then go to fastboot again and install xiaomi.eu a12 version.
This is exactly why I hate fastboot method and always install rom from twrp
Flash 14.0.5 via orangefox recovery.
I left it overnight and nothing happened . I disconnected the phone and it rebooted ok. I am kind of worried about trying again. Is the twrp method safer ?
Just discovered that I stupidly set the "USB debugging (Security settings) on but I forgot to turn on "USB debugging" which is a few lines above in settings. Could that be what has stopped the process?
Phone should flash fine even if debugging is off. I would recommend you to make sure that the cable doesnt even move an inch during the whole flashing process as that sometimes interrupts it especially if you have a loose port.
I just switched the usb port from the back of the pc (which I think are USB 3.0) to the front panel of the PC (I suspect USB 2.0 ) and tried flashing the MIUI 14 from yesterday again - It worked !!!!
*Deleted
Hi,
You could check out my post,
Fastboot not working in Windows 11 [Resolved]
Hello! I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this? It shows up as 'Android' in device manager. I've also attempted to install a drivers manually...
forum.xda-developers.com
I hope it might help for the future
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Carl_OX said:
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Click to expand...
Click to collapse
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
mogamycool said:
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks... I really appreciate the early reply.
But can't I do this using the recovery method? And also must the android and miui versions of both the global stock rom and custom rom be the same?
Nevermind...thanks for your help
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
mogamycool said:
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
Click to expand...
Click to collapse
Thanks boss