Hello Guys.
At the beginning of 2020 I acquired a Xiaomi Mi9 SE through AliExpress. The device came in perfect state and it kept like that until I found out that the ROM of the device was not an official one (something I was suspecting because the device had its bootloader unlocked). Knowing this I decided to flash an official ROM downloaded directly from Xiaomi’s web site. First I tried doing it in recovery mode through the update menu on MIUI 11 settings, but the device (I am guessing the custom ROM) did not allow me to do it due to some carrier related error. After this I tried using a VPN which, of course, did not fix the issue.
I did a bit more research and decided to flash the ROM through fastboot mode. I downloaded the needed ROM and Xiaomi’s Mi Flash Tool to a Xiaomi Mi 13 laptop (with Windows 10) and made all the needed steps. All went with no issues and the device rebooted, but when that happened my phone was stuck in, what I have identified as a, soft brick. So now I have the device in a bootloop on recovery mode and can only access to fastboot mode. The device has had its bootloader locked because I forgot to select an alternative option to “flash + lock” in Mi Flash Tool (my fault).
Since then I have been quite busy and have not been able to focus on the problem as I wished. I have done some research but most of the info I found is directed towards Windows users, which is now a problem because I no longer have easy access to the Windows laptop previously mentioned (my current working machine is an Arch Linux laptop). Also most solutions I found require using the test points method to force EDL mode on the phone which I found quite difficult to do. Taking into account that I have no tools to perform the task and the current lock-down situation makes it quite difficult to obtain the aforementioned tools, this solution does not seem suited for the context.
*I have attached a video with the current state of the phone.*
[Soft brick – Mi9 SE](https://reddit.com/link/gabeat/video/jlqhaholxrv41/player)
Being in my current situation I have made research on how to perform ROM flashing in Linux and seems pretty easy (easier than the Windows solution). But whenever I try flashing the ROM using the shell script (`sh flash_all.sh`) my terminal just stays in blank prompt:
❯ sh flash_all.sh
When I run `sudo fastboot devices` my phone is detected:
❯ sudo fastboot devices
[sudo] password for angel:
485fd7a8 fastboot
I really have no clue of how to fix this problem. I would really appreciate some help from you guys. This is being quite frustrating because the phone is just a few months old and it was working flawlessly.
PD: Sorry for my English it is not my mother tongue.
UPDATE:
So I have been working in the issue again and I have made an improvement (sort of). When I run `sudo sh flash_all.sh` I am getting this:
~/Downloads/grus_global_images_V11.0.2.0.QFBMIXM_20200310.0000.00_10.0_global
❯ sudo sh flash_all.sh
Missmatching image and device
UPDATE:
I have tried to run the script again and it is showing the blank prompt once again.
UPDATE:
So I am finally able to run the script by, firstly, wiping all data from the recovery mode menu, then booting into fastboot mode. After that I run the script with the device not yet connected to my PC and after starting the script I connect the device. This is when, if I have commented one particular line regarding the **Missmatching image and device** error from the script code, the device does something: goes to a black screen with an unreadable (it is cut by the screen edge) error message on the top right corner of the screen. If I click power button after this error message the device reboots to recovery mode. On the contrary if I left the code untouched is when my terminal returns the error message **Missmatching image and device** and the phone just does not do anything.
UPDATE:
So far what I have been able to gather is that the only possible way to unbrick the device is by going into EDL mode. For that you need an authorized Mi Account which is no longer given out by Xiaomi to normal users. So the problem now is finding someone who has this authorization and that is willing to help.
LAST UPDATE:
I finally got in contact with a smartphone repair shop in my hometown now that all the COVID-19 thing is somewhat over in Spain. The shop guy charge me around 30€ and it took around 2 weeks to be repaired due to the phone being sent to Madrid for someone with the permissions in its mi account to make all de EDL mode thing and install an European ROM.
So long story short: find someone or some repair shop near you and let them repair ir for you.
As it has been said already in the comments the problem it is not really related to the computer OS.
So happy to see the help coming from every where, you guys dam good.
Yo Horta try unlocking with mi unlock tool. Afterwards you could flash twrp recovery and flash a rom that way or flash the correct rom with Xiaomi flash tool.
If the unlocking process fails try with olders mi unlock tools you could find around internet. I hope you fix this man
From my experience as long as it’s the same device model you can actually cross flash vendors, which is typically not recommended but when I cross flashed the CN vendor for my Redmi K20 Pro (Raphael) I didn’t encounter any issues.
I did some googling your device which is Xiaomi Mi 9 SE whose code name is grus from what I read, that’s what you should look up on mifirm.net.
From my knowledge, I don’t think you’ll be able to use the Mi Flash Tool to unbrick your device, likely you’ll have to pay someone with a registered EDL Account to unbrick it, given Xiaomi’s limited presence in the EU.
Do you still have the same problem?
Really sucks man but it is what it is. I will try finding a solution with what you have told me about the authorization to go into EDL mode. I really appreciate it man. Thanks for taking the time to answer.
[Xiaomi flash tool for Linux systems](https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847)
the best method would be to do a windows VM and pass the USB post where the device is connected to the VM. you can try miflash.exe with wine but it will probably don’t work.
the edl pin useless for us (simple user) because you need a Xiaomi authorized account to reflash in edl mode. the authorized account are only given to store or employee.
You should have used twrp recovery or something else if bootloader was already unlocked.
Yeah definitely the computer OS is not an issue, aside from the available tools. With the info I have gather I really think that EDL is my only option. Just one question will it be possible to unlock the bootloader with the Xiaomi Tool? And will that helping the issue guessing that the current flashed ROM was made for a variant of the Mi 9 SE from another region?
Yeah I know that. I am just making it explicit that my working PC is a Linux one so the ones who read the post can help me solving the issue.
what’s the error ? I think you already google it since your a fellow linux user but who knows. in miflash you want to flash without saving data, to wipe everything on the phone, for me when i flash with saving user data it doesn’t boot. don’t forget to do backup before flashing
That’s why i prefer Windows to Linux
I live in Spain. I have made some googling to try finding technical assistance but I think is not yet available officially in my country. As for the EDL stuff, well is an alternative. I have not really dug deep in that subject yet so I am quite lost when it comes to it.
As others have said already, EDL mode is your only option.
Since you locked the bootloader, fastboot won’t let you flash anything that isn’t the same or an upgraded version of the ROM you flashes before locking it – but the ROM you flashes before locking it is either broken, or made for a variant of the Mi 9 SE from another region.
The only way to bypass that is to flash it with EDL mode, which doesn’t verify anything.
Install wine on your linux system and use it to run the xiaomi flash tool on your linux system. This way you’ll be able to run the exe on your linux system.
I don’t know if it’s gonna work, but I managed to flash a ROM in the past on Linux with the same method, I also had the blank prompt, and if i remember correctly i fixed it by running the script first and then booting in fastboot.
I know a guy who can help you.
You need to download the CORRECT rom. Remove the back cover to have access to the EDL test points. A computer with TeamViewer installed.
He will log in to your computer using TeamViewer and use his Authorized Mi Account to load the rom on for you.
It was the only solution for my sons bricked Redmi Note 8. It cost me NZ$70.
I will give it a try but it seems that the available Mi Unlock tool on Linux does not have this feature implemented. So I will need to get my hands on a Windows machine. Thanks mate, I will keep you updated with what I find out.
Yeah mate, no improvements 🙁
Are you sure you have the correct rom? You should look at your box for extra info, maybe the seller lied and the phone isnt global. Also if you use the test point method, changes are high that you will need to set imei number back to the original value on the box ( Can get ereased when hardbricked). It happened to my redmi note 4x lol, I had to download an app from google play something like imei changer to set it back ( did also require me to root the device).
I get it, they’ve made it so much complicated for something that should be done pretty easily. Plus if they fill their software with so many ads and useless chinese stuff they should know that people are gonna flash custom roms and take risks. I was very satisfied of the phone for the price but making it literally useless because of one mistake is just disgusting.
You might have some hope with aftermarket roms. Flash twrp or orangefox and try havoc, evolution, PE, whatever. Just make sure it’s the same device codename.
With mi flash tool you can fix it. Only connect the phone to the computer and flash it. The same thing happened to me. But I don’t remember if you need your Xiaomi unlocked.
Hello, well a guy contacted me and told me about someone in Ukraine that charged him 70NZ for the repair (which was successful). The thing is that you need to open up the phone, unplug the battery and perform the test point method while you let the Ukraine guy control your PC via TeamViewer so he can use his authorized account and do all the stuff. I am guessing this need to be done on a Windows machine.
It is global and I have downloaded the global version. The thing is as I wrote on the post, that my phone came from third party, it was not bought on an official Xiaomi store. As I have also written in the post the phone came with an unofficial ROM installed, so the issue begun when trying to change this ROM to an official one.
Can I flash custom recoveries like TWRP with my booloader locked?
you will have more chance of success on windows, that why I suggested using a VM to use windows even on Linux. Linux isn’t officially supported by any Xiaomi tool sadly, and I don’t even known where your .sh come from. I’m not surprised it doesn’t work on windows as it’s not designed to, sadly
Dam fuck
The seller used a custom ROM so you can imagine… I won’t do the test points method unless not until I have ran out of other options. But thanks mate!
Yeah I have learnt it the hard way…
Thanks for the comment but my device is being detected both in fastboot and ADB mode.
Do you remember if the tool had other options. Just so I can make some troubleshooting.
SORRY can’t help but send you all my power buddies, hope you gonna fix this.
It’ll throw a error because you can’t flash any rom either recovery or fastboot with a locked bootloader. It has nothing to do with Linux or Windows the only way you can fix it is to use Mi unlock tool and unlock your bootloader from there reflash fastboot rom and don’t make the same mistake again. Sometimes if bootloader has been unlocked before which it has in your case the unlock can be instant but usually theirs a waiting period with Xiaomi. It’s a rough lesson where one simple mistake can cost a massive headache been through it before.
Also you might have to contact the person you bought it from because of some other Xiaomi bullshit where the phone is linked with their mi account but that’s a worse case scenario.
what’s the problem you were facing in windows ? that even after the flash it doesn’t boot ?
Aaahhhhh… No, not really, not that I know of. You’re gonna kinda wanna Google your way out of this one.
When I tried to flash a the ROM again (seeing that my device was bricked) with Mi Flash Tool it just prompt an error and did no do anything. So yes in Windows (which I do not think is the problem) my device did not boot after flashing the ROM
And your phone is global, correct? Flash the according region rom too, that matters.
Yeah I was afraid that was be the problem. Test points is clearly not an option right now so I’ll see if I can contact with someone who can fix the issue. Thanks man.
That is what I think but the ROM was downloaded from Xiaomi and it is for the specific terminal and specific mode (fastboot). Eitherway now it is just not doing anything when I run the script.
I’m not expert… But don’t you need set file patch to ROM (or at least run terminal in that location)?
Did you set premission of script to a+x?
I looks like the Mi recovery doesn’t support booting into EDL mode either.
I’m out of ideas – I hope you find something.
Srry for that. But I am just trying to make people aware so they don’t do the same thing. Unfortunately I have no idea what to do here, 😬, srry.
Yeah I guessed so. Well thank you very much mate. I will try unlocking the bootloader from a Windows PC and if turns out impossible I will do some research on the EDL stuff.
Appreciate it mate. In order to go in EDL mode I need to perform the test point method? Or are there other ways? I remember watching a video on YouTube where a guy running Windows ran a batch file (.bat) that made the device (an old xiaomi) go into EDL mode – don’t know if that is currently possible. Thanks again.
I can get to Xiaomi recovery and access Mi Assistant, but running `adb reboot edl` returns:
❯ sudo adb reboot edl
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
As for `fastboot oem edl`:
❯ sudo fastboot oem edl
FAILED (remote: ‘Error Invalid Parameter’)
fastboot: error: Command failed
If I try using without `sudo` it just keeps waiting for a device but `sudo fastboot devices` returns:
❯ sudo fastboot devices
485fd7a8 fastboot
As for the complication you explained I am aware of the complications it may carry. So I will see what can be done some other user have suggested asking for the authorization via XDA forums, who knows..
Wow, what a doozy.. probably don’t buy your electronics from Ali Express anymore? 🙂 Amazon treated my phone right and it came with clean MiUI. Granted I’ve flashed it with a clean version of MiUI basically ensuring it’s clean, but it ran an original rom to begin with.
I can help. PM me.
I did not. I think is too much hustle for fixing a software issue. I mean I don’t really want to ever use a Xiaomi phone again seeing how hard they are trying to make life harder for their users. Apart from that I don’t have the tools to open my phone up. And even if I did decide to contact this guy I have no guarantee that my phone is going to be fixed.
When I did that with Mi Flash Tool a second time (after seeing the issue) on Windows it returned an error I cannot remember it now. The thing is it is now very inconvenient for me to access to a Windows machine and I am trying to solve the problem on a Arch Linux Machine.
Well I didn’t know that but I really didn’t want to have an unofficial ROM because who knew what they could be doing.
Some phones can boot into EDL mode from custom recoveries, but that doesn’t really help in this situation.
You can try the `fasboot oem edl` command in fastboot.
If you can get into the Xiaomi recovery, you can try looking at translated screenshots online to select the “Mi Assistant” option, which should enable ADB – from there, you can try `adb reboot edl`.
There’s also another complication that I forgot about. Modern Xiaomi phones, (probably including yours) need the Xiaomi software specifically to be flashes in EDL mode. That software needs to be signed into with an authorised Mi account. Xiaomi used to give out authorisations to people who asked on their forums, but they don’t anymore – you’ll need to buy one online (through a third party).
Contact @miauthofficial on Telegram
They’ll flash your device in no time
Okay thanks for the quick reply and for the post link. I downloaded **android-udev** from the official Arch repos and didn’t do anything more just for testing. After running `sudo adb reboot edl` I got this output:
❯ sudo adb reboot edl
reboot.
The device rebooted and went back to recovery mode. Everything looks the same as before doing the reboot.
The ROM I got was from this [site](https://xiaomifirmwareupdater.com/miui/) because when I tried to get it from the official MIUI site it just redirected me to a page presenting MIUI 12. I check the shell code and it looks for the keyword grus which is the keyword name for my device if I am not mistaken,
Your safest bet would be to get a Xiaomi service center if there is one near you, but if you don’t have one near your go ask around on XDA or Telegram for people that might authorised account for EDL
I suggest getting your roms whether they be fastboot or firmware files from mifirm.net much more reliable and hasn’t failed me yet. Although likely EDL method may be your only way out, because the Bootloader locked itself which is why you can’t boot into it at all.
I doubt the disparities of Linux or Windows are the main issue here. Look more into EDL, and just be careful with the Mi Flash Tool it really isn’t designed well, with selecting the flash and lock option off the bat….
I cannot attach images but I will try describing it to you. The utility has two options:
1. **My device works normally. I want to mod it**: requires USB debugging so does not seem like the fix.
2. **My device is bricked. I want to unbrick it**: when I choose this options it promts a popup saying **Feature not available yet**.
That is why I ended up discarding this option. Thank you anyway.
Yeah I tried using the Chinese ROM but I was getting the Mismatch error too. Which unlock tool are you talking about? Is it [XiaoMiTool V2](https://www.xiaomitool.com/V2/)?
It’s alright mate. Thanks for spending the time in helping me. I will try to find out a way to get in contact with someone who can help me with the EDL stuff.
the modification of the .bat file seams legit, plus it’s just commenting 2 lines you can easily do it.
you get missamtching image and device with miflash too ? on the thread you linked one guys said he had issue with AMD cpu
Don not know what you talking about? Can you be more specific?
I cannot tell you if I got the same error with Mi Flash Tool as I use it on the Windows laptop I mentioned on the post like a month ago and I have no access to other Windows PC at the moment. Regarding the CPU, no, my PC is using Intel i7 5500u.
Sorry mate flashing the incorrect rom on a device and locking the device will cause a hard brick, since you locked your bootloader you won’t be able to flash anything. Only EDL mode can save you, so you either have to go to Xiaomi service center or find some one on the internet who has an authorized account for flashing in EDL mode or you have to figure out making the test point work.
Please if you are going to comment try to be helpful. This post will not only help me but future users will too.
Wine cannot access USB devices. It should also not be used for software that can permanently damage devices if there are problems!
I’m not sure but if it said “Missmatch etc.” doesn’t that mean that it actually detected the phone in fastboot? Maybe it’s the wrong ROM
The problem is with your phone not with windows.
It looks like your phone doesn’t have an EFDL fastboot command, so that’s not an option anymore.
As for the ADB error, it looks like you’re missing udev rules. IIRC, you said you were on Arch? Take a look at [this wiki page](https://wiki.archlinux.org/index.php/Android_Debug_Bridge#Adding_udev_rules).
Damn the x2 looks nice
I had a similar problem a few weeks ago, I had fastboot/adb but unable to be detected in Linux/windows. In the mi9se telegram channel they told me that probably I fried the USB-C connector ( data was not transfer so I couldn’t get the device recognized) . So I replaced the part and now works perfect.
I was referring to the original MiUnlock tool by Xiaomi. The website you linked to is a little weird, according to the feature list it can unlock the bootloader just like the official tool, but on the other hand the website states that one should use the official MiUnlock tool in your situation just a little further:
>But there are cases in which there is no direct way to unbrick your device: the infamous “This MIUI version can’t be installed on this device” is the result of Global rom being installed on Chinese hardware with locked bootloader. In that case XiaoMiTool V2 would be able to flash only another Global rom (because of Xiaomi region enforcement), and that would be useless since the problem (Global rom/chinese hardware) would remain and the device would not boot.
The only options in this case are:
>A) if you bound a Xiaomi account to your device in the developer setting before brick, then you should be able to use MiUnlock (and in the future XiaoMiTool V2 too) to unlock your device. This is your best option, so always remember to bind your device to your Xiaomi account!
Only works when the account was bound to the device though.
Totally agreed. Well if you are looking for a phone check out Realme, lol
Thanks for your quick reply, sending 70$ to a random Ukraine guy kinda looks like a scam haha, but I guess I’ll have to do that if there’s really no other solution. Did you do it?
I tried doing the script modification. In linux is a shell script which code looks like this:
fastboot $* getvar product 2>&1 | grep “^product: *grus”
if [ $? -ne 0 ] ; then echo “Missmatching image and device”; exit 1; fi
CURRENT_ANTI_VER=1
ver=`fastboot $* getvar anti 2>&1 | grep -oP “anti: \K[0-9]+”`
if [ -z “$ver” ]; then ver=0; fi
if [ $ver -gt $CURRENT_ANTI_VER ]; then echo “current device antirollback version is greater then this pakcage”; exit 1; fi
fastboot $* erase boot
if [ $? -ne 0 ] ; then echo “Erase boot error”; exit 1; fi
fastboot $* flash crclist `dirname $0`/images/crclist.txt
if [ $? -ne 0 ] ; then echo “Flash crclist error”; exit 1; fi
fastboot $* flash sparsecrclist `dirname $0`/images/sparsecrclist.txt
if [ $? -ne 0 ] ; then echo “Flash sparsecrclist error”; exit 1; fi
fastboot $* flash xbl `dirname $0`/images/xbl.elf
if [ $? -ne 0 ] ; then echo “Flash xbl error”; exit 1; fi
fastboot $* flash xblbak `dirname $0`/images/xbl.elf
if [ $? -ne 0 ] ; then echo “Flash xblbak error”; exit 1; fi
fastboot $* flash xbl_config `dirname $0`/images/xbl_config.elf
if [ $? -ne 0 ] ; then echo “Flash xbl_config error”; exit 1; fi
fastboot $* flash xbl_configbak `dirname $0`/images/xbl_config.elf
if [ $? -ne 0 ] ; then echo “Flash xbl_configbak error”; exit 1; fi
fastboot $* flash abl `dirname $0`/images/abl.elf
if [ $? -ne 0 ] ; then echo “Flash abl error”; exit 1; fi
fastboot $* flash ablbak `dirname $0`/images/abl.elf
if [ $? -ne 0 ] ; then echo “Flash ablbak error”; exit 1; fi
fastboot $* flash tz `dirname $0`/images/tz.mbn
if [ $? -ne 0 ] ; then echo “Flash tz error”; exit 1; fi
fastboot $* flash tzbak `dirname $0`/images/tz.mbn
if [ $? -ne 0 ] ; then echo “Flash tzbak error”; exit 1; fi
fastboot $* flash hyp `dirname $0`/images/hyp.mbn
if [ $? -ne 0 ] ; then echo “Flash hyp error”; exit 1; fi
fastboot $* flash hypbak `dirname $0`/images/hyp.mbn
if [ $? -ne 0 ] ; then echo “Flash hypbak error”; exit 1; fi
fastboot $* flash devcfg `dirname $0`/images/devcfg.mbn
if [ $? -ne 0 ] ; then echo “Flash devcfg error”; exit 1; fi
fastboot $* flash devcfgbak `dirname $0`/images/devcfg.mbn
if [ $? -ne 0 ] ; then echo “Flash devcfgbak error”; exit 1; fi
fastboot $* flash storsec `dirname $0`/images/storsec.mbn
if [ $? -ne 0 ] ; then echo “Flash storsec error”; exit 1; fi
fastboot $* flash storsecbak `dirname $0`/images/storsec.mbn
if [ $? -ne 0 ] ; then echo “Flash storsecbak error”; exit 1; fi
fastboot $* flash bluetooth `dirname $0`/images/BTFM.bin
if [ $? -ne 0 ] ; then echo “Flash bluetooth error”; exit 1; fi
fastboot $* flash cmnlib `dirname $0`/images/cmnlib.mbn
if [ $? -ne 0 ] ; then echo “Flash cmnlib error”; exit 1; fi
fastboot $* flash cmnlibbak `dirname $0`/images/cmnlib.mbn
if [ $? -ne 0 ] ; then echo “Flash cmnlibbak error”; exit 1; fi
fastboot $* flash cmnlib64 `dirname $0`/images/cmnlib64.mbn
if [ $? -ne 0 ] ; then echo “Flash cmnlib64 error”; exit 1; fi
fastboot $* flash cmnlib64bak `dirname $0`/images/cmnlib64.mbn
if [ $? -ne 0 ] ; then echo “Flash cmnlib64bak error”; exit 1; fi
fastboot $* flash modem `dirname $0`/images/NON-HLOS.bin
if [ $? -ne 0 ] ; then echo “Flash modem error”; exit 1; fi
fastboot $* flash dsp `dirname $0`/images/dspso.bin
if [ $? -ne 0 ] ; then echo “Flash dsp error”; exit 1; fi
fastboot $* flash keymaster `dirname $0`/images/keymaster64.mbn
if [ $? -ne 0 ] ; then echo “Flash keymaster error”; exit 1; fi
fastboot $* flash keymasterbak `dirname $0`/images/keymaster64.mbn
if [ $? -ne 0 ] ; then echo “Flash keymaterbak error”; exit 1; fi
fastboot $* flash logo `dirname $0`/images/logo.img
if [ $? -ne 0 ] ; then echo “Flash logo error”; exit 1; fi
#fastboot $* flash splash `dirname $0`/images/splash.img
#if [ $? -ne 0 ] ; then echo “Flash splash error”; exit 1; fi
fastboot $* flash misc `dirname $0`/images/misc.img
if [ $? -ne 0 ] ; then echo “Flash misc error”; exit 1; fi
fastboot $* flash aop `dirname $0`/images/aop.mbn
if [ $? -ne 0 ] ; then echo “Flash aop error”; exit 1; fi
fastboot $* flash aopbak `dirname $0`/images/aop.mbn
if [ $? -ne 0 ] ; then echo “Flash aopbak error”; exit 1; fi
fastboot $* flash qupfw `dirname $0`/images/qupv3fw.elf
if [ $? -ne 0 ] ; then echo “Flash qupfw error”; exit 1; fi
fastboot $* flash qupfwbak `dirname $0`/images/qupv3fw.elf
if [ $? -ne 0 ] ; then echo “Flash qupfwbak error”; exit 1; fi
fastboot $* flash vendor `dirname $0`/images/vendor.img
if [ $? -ne 0 ] ; then echo “Flash vendor error”; exit 1; fi
fastboot $* flash vbmeta `dirname $0`/images/vbmeta.img
if [ $? -ne 0 ] ; then echo “Flash vbmeta error”; exit 1; fi
fastboot $* flash dtbo `dirname $0`/images/dtbo.img
if [ $? -ne 0 ] ; then echo “Flash dtbo error”; exit 1; fi
fastboot $* flash system `dirname $0`/images/system.img
if [ $? -ne 0 ] ; then echo “Flash system error”; exit 1; fi
fastboot $* flash cache `dirname $0`/images/cache.img
if [ $? -ne 0 ] ; then echo “Flash cache error”; exit 1; fi
fastboot $* flash userdata `dirname $0`/images/userdata.img
if [ $? -ne 0 ] ; then echo “Flash userdata error”; exit 1; fi
fastboot $* flash recovery `dirname $0`/images/recovery.img
if [ $? -ne 0 ] ; then echo “Flash recovery error”; exit 1; fi
fastboot $* erase sec
if [ $? -ne 0 ] ; then echo “Erase sec error”; exit 1; fi
fastboot $* flash cust `dirname $0`/images/cust.img
if [ $? -ne 0 ] ; then echo “Flash cust error”; exit 1; fi
fastboot $* flash boot `dirname $0`/images/boot.img
if [ $? -ne 0 ] ; then echo “Flash boot error”; exit 1; fi
fastboot $* flash logfs `dirname $0`/images/logfs_ufs_8mb.bin
if [ $? -ne 0 ] ; then echo “Flash logfs error”; exit 1; fi
fastboot $* reboot
if [ $? -ne 0 ] ; then echo “Reboot error”; exit 1; fi
But even when the script finally runs, the device (not the terminal) returns the same error: a black screen with an unreadable, too small to read text at the top right corner.
No. Xiaomi only issues Authorized accounts to official Xiaomi service technicians as far as I know.
Of course is not working on Windows. I am running the script on Linux. I could install a Windows virtual machines, of course, but I don’t really think the problem relays on the computer OS. However I will try to find an Windows ISO an create a virtual machine.
#Here’s how to fix your phone with a custom ROM!
Custom ROMs are usually what people flash onto their devices as soon as they can get their bootloader unlocked, to get rid of MIUI. You already have it unlocked 😉 Xiaomi hardly makes a profit on it’s cheap phones, so they make back money through MIUI. MIUI’s ads (tons in some regions!) and tracking earn them money, while violating your privacy and eating up battery & ram! It’s also pretty bloated. A custom ROM will give you a Google Pixel like experience, with clean Android. I’m here to help you out through every step. If you need _any_ help, feel free to ask 🙂
1. First things first, choose your weapon- Either boot into a Windows VM (it takes just a couple of minutes to make!) or do this in your Linux terminal. The instructions have the exact statements for Windows, so if you’re using Linux you’ll need to do a bit of Googling. I recommend you use Windows for now 🙂
2. Google “Mi 9SE XDA”. You’ll find the XDA page for your device there. XDA is a site where you can download custom ROMs and stuff for your device! Here’s the most popular ROM for your device – crDroid!
https://forum.xda-developers.com/mi-9-se/development/rom-crdroid-v5-6-t3951589
You’ll also need a custom recovery like TWRP to flash the ROM. Here’s TWRP for your device:
https://forum.xda-developers.com/mi-9-se/development/recovery-unofficial-twrp-3-3-1-0-t3935470
You may also want to flash Magisk of you want root. Here’s Magisk! (Optional)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
Lastly, you need to flash GApps (Google Apps) on your device to get the PlayStore etc. Download the Arm64, Android 10, Nano package from here:
https://opengapps.org/
3. Now that you have the files download and ready from the respective websites, you just need to flash TWRP. Boot into fastboot, plug in your phone, and type the code in the “instructions” part of the TWRP link. You’ll need to flash vb meta first for your device, followed by TWRP. The instructions there are pretty clear!
4. After you flash TWRP, you’ll need to flash your ROM using it. In the crDroid website, again under instructions, you’ll find out what exactly you need to do in TWRP. With TWRP’s GUI, you’ll generally need to wipe everything on your device, copy over your ROM, GApps and Magisk from your PC (it will show up on your pc as a storage device when you plug it in!) Then, flash your ROM, followed by GApps, followed by Magisk which is optional. And reboot!
5. That’s it! It’s pretty straightforward, and again, if you have _any_ trouble feel free to ask 🙂 Enjoy a clean, fast phone!
#Edit-
Oh crap! After all this, I realised that your BL was locked 🙁 Mi Flash should work even with a locked BL, as long as you’re switching bw MIUI. The error you had should be because you either download the wrong device’s rom from their website, or it’s not a Mi 9SE and the seller lied to you. I suspect it’s the former, so re-download your ROM and try again!
If this doesn’t work, you’ll need to use EDL.
Once you boot into MIUI, get get your bootloader unlocked, and flash a custom ROM! Trust me, it’s worth it 😛
Ok, so you have a device
1. from AliExpress
2. shipped with modified firmware
3. bootloader was unlocked or unlocked and relocked
4. Missmatching image and device
Have you tried to flash the Chinese ROM? Because that sounds a lot like a chinese model flashed with a global ROM.
Edit: nvm, saw that you locked the bootloader. If you can’t unlock it again it’s a case for EDL. I couldn’t get the unlock tool to work in Linux (actually it didn’t work on my Ryzen laptop at all) but your mileage may vary.
Ah sorry! I did not see that. In that case maybe he can install it on an [external hard drive](https://www.google.com/amp/s/www.trishtech.com/2018/12/how-to-install-windows-10-from-an-external-hard-drive/amp/)?
When I manage to make the script recognize the device in fastboot and avoid the blank prompt I describe on the post the error I get is the following:
❯ sudo sh flash_all.sh
[sudo] password for angel:
Missmatching image and device
I have found some results on the Internet about the issue. As far as I can tell some people advise to touch the script code but I am quite concern with doing something like that. This is [one](https://forum.xda-developers.com/redmi-note-4/help/getting-mismatched-image-error-fastboot-t3638653) of the posts I have read, I trust XDA but still..
The script is inside the decompressed .tgz ROM file so I run it in that location. And yes I did change the permissions if had not I am pretty sure that the terminal would have thrown an error.
Already done that. The problem is not with the computer OS. However there are online guides to perform ROM flashing on Linux.
He mentioned it being a work laptop, I can imagine it’s from his workplace thus messing with it could be problematic.
The link you shared is for Debian based Linux distros, mine being Arch cannot use that kind of runfiles. However there is a version uploaded to AUR I will try with it.
Is there a reason why you can’t partition your drive and install windows? You can get the ISO for free from Microsoft. Once you are done, remove the partition.
My life in one comment. LOL
That is not a really helpful comment 😐
Look at the post comments maybe you find something useful. This [one](https://www.reddit.com/r/Xiaomi/comments/gabeat/bricked_xiaomi_mi9_s_how_to_fix_on_linux/fozhcld?utm_source=share&utm_medium=web2x) is probably the most useful I have read. Well maybe not useful to fix the problem but it definitely clears out some doubts.
Hey dude, I’m running into the same problem, EDL flashing seems to be the only way out as far as I understand. Have you managed to get your phone back with this method ? If so, did you find someone with a real Xiaomi authorized account ?
Thanks in advance, I’d really appreciate some help 😉
I think that either using Windows or Linux a will have the same problem. I tried flashing a ROM in Windows in the past and there was no way.
I tried the tool already but I got ir from XDA I will see if that maybe fixes it. Thanks! I will keep you updated.
Thanks for the suggestion, but sadly that does not work it just maintains the blank prompt. Checkout the update I have made in the post maybe it rings a bell.
It seems to be the only solution as I have read in other comments in the post. So I will look into it. Do you know some way I can contact someone with the aforementioned EDL Account?
That sucks, cant you return the device because if you cant go into edl mode you can kiss you device goodbye
Thanks man, I suppose you upvoted the post, it not please do so it reaches more people. Thanks again for the support.
Hahahaha the only solution I have is to have someone remotely control my PC, disassemble my device with tools I don’t have and without any guarantee of success in the process. So I just prefer to not expend any more time nor money in this.