Develop Bugs

Mi Max Stuck On Mi Logo and Bootloop

Hi Guys. I have a problem with my Mi Max 32/3gb. After OTA update it stucks on bootloop while the boot loader was locked and unrooted. I tried every method found in c.Mi.com and xda websites. nothing helped me to overcome this problem. I could enter to fastboot and also EDL modes, I also opened the back cover to remove the battery and shorting the test points but no luck. In fastboot mode I got error because the bootloader was locked, while in EDL mode I could successfully flash the fastboot roms including Ch_Dev, Ch_sta, Glob_Dev, and Glob_sta, but after turning on the phone, it shows bootloop again and again. But on time accidentally my phone loaded on boot and came alive (I don't know how!!). this time I first signed in with my mi account and applied for unlocking bootloader, then factory rested the device to see if it boot-up again or not. unfortunately it again stucked on bootloop. After unlocking the bootloader, I tried recovery roms using mi PC suite beta (Chinese version) which got error says something like your bootloader is locked (but it is not), Also I tried loading recovery rom using TWRP which the procedure stucks at "package_extract_file took 00s" for about 60mins and nothing happen. the only differences between all of these methods is bootloop at MI logo, bootloop at Mi logo and android logo with three blinking dots, freeze at MI logo, and freeze at Mi logo and android logo with three blinking dots. Any Idea?

Clear data after flashing, also only use save userdata when flashing fast boot rom

MM.626 said:
Clear data after flashing, also only use save userdata when flashing fast boot rom
Click to expand...
Click to collapse
Thank you for your reply. Tried before but not helped.
I can flash fast boot rom successfully in Fastboot and edl modes using Mi flash tools beta and also Mi PC suit without any error, but the phone cannot boot and still freeze at mi logo and some time bootloop. Flashing recovery rom is not possible in recovery mode even using TWRP and Mi PC suit, freeze in the beginning of flashing. How can I check to see if all necessary files of fast boot rom were copies to memory? I thing some thing force memory to lock especially in recovery mode!!!!
Any idea?

Maybe you should unlock the bootloader?

MM.626 said:
Maybe you should unlock the bootloader?
Click to expand...
Click to collapse
The bootloader has already been unlocked. No difference, still freeze at mi logo.
It is also weired, why I cannot flash recovery rom!! Geuse there is something wrong.

lordcx said:
The bootloader has already been unlocked. No difference, still freeze at mi logo.
It is also weired, why I cannot flash recovery rom!! Geuse there is something wrong.
Click to expand...
Click to collapse
i know, i just went back to miui9 from nitrogen oreo last week, my bootloader was unlocked too. but mine also couldn't boot past mi logo, so i tried everything like you did, the only thing worked for me was to re-unlock bootloader, flash fastboot rom, clear data in recovery, reboot.

MM.626 said:
i know, i just went back to miui9 from nitrogen oreo last week, my bootloader was unlocked too. but mine also couldn't boot past mi logo, so i tried everything like you did, the only thing worked for me was to re-unlock bootloader, flash fastboot rom, clear data in recovery, reboot.
Click to expand...
Click to collapse
You mean you used clean_all and lock option at miflash tool and then re-unlocked it using mi unlock tool again?
Can you explain more? I have not lock the bootloader again fearing cannot relock it for the next time.

Any luck here ?
Did you test flashing miui 8 ?

No luck, I tried evey methodes and evey roms, but no luck

Did you send it to service center ?

head_djmusic said:
Did you send it to service center ?
Click to expand...
Click to collapse
No it was out of warranty.
I sold it for spare parts. Sad story.

Sad
lordcx said:
No it was out of warranty.
I sold it for spare parts. Sad story.
Click to expand...
Click to collapse
Well, i will test with QFIL and if it didn't solve the problem, i will sell it as spare, too!
And life is going on!

head_djmusic said:
Well, i will test with QFIL and if it didn't solve the problem, i will sell it as spare, too!
And life is going on!
Click to expand...
Click to collapse
I have tested with qfil too, it returned an error for data partition, i do not remmember the exact massage but I could not find any solotion for it. Seems my partitions was write protected or something like that. Hope you can resolve yours and let me know if you need my experiance.

Thanks, Seems the problem is from BOOT Partition, i will sell it as spare part, too !
Thanks for your help friend

Update to Global 9.5.4.0 and Factory reset ends in a bootloop

Hi, I have a serious problem here and maybe somebody has an idea.
Recently i upgraded via provided OTA update to 9.5.4.0 and everything seem to work fine, but I did afterwards a factory reset (via the menu of the phone) to the device- Mi account was deleted and bootloader is locked.
So i didn´t play at all with the mobile before.
I already requested now (after the problem occured) the unlock of the bootloader and got the feedback of Xiaomi that i can use now the Unlocker tool.
Unfortunately the device needs to have an MI account binding to use the Unlocker tool.
After the factory reset the device starts from scratch and i get the famous MIUI9 beginning screen, can choose the language and the region. Then the device try approx. 30 times to continue and end always with a message (only for some seconds): "Find Device closed unexpectedly". After approx. 30 times im ending up in the MI-Recovery 3.0 where i can choose REBOOT, WIPE DATA, CONNECT WITH MI ASSISTANT (PC-SUITE)
REBOOT: will do again 30 times the message: "Find Device closed unexpectedly"
WIPE DATA: starts from the choose of language and region again and it doesn´t matter which language i choose ends up in the MI-Recovery 3.0
CONNECT WITH MI ASSISTANT: ends up with the english version, that i can´t connect, but with the Chinese version, i can at least open the downloaded ROM 9.5.4.0 and start the flashing process which hang up immediately and doesn´t go beyond 0%. It ends up with some chinese messages i can´t read
FASTBOOT could be reached by pressing Vol- + On/Off, but doesn´t help with a locked bootloader i guess
So if anybody have an idea how to overcome the situation it would be quite helpful.
Thx

I think you can flash fastboot miui rom with locked bootloader, just search the google for procedure, you would need to delete some lines in bat file for it to work. You will loose all data of the phone for sure, and you will need a miflash tool. After that you are good as new. It might be an issue that you have not enabled developer part. If this doesnt work, try to flash a recovery image via original recovery, i think i saw it somewhere ( cant post url)..

Yes, please share the link if possible, esp. the information about the BAT file, cause actually i searched since days and tried from MiFlash Tool until QFil everything.
I got developer part enabled before, but doing a reset to factory doesn´t allow me to re-enable anything.
How to flash something from original recovery, cause i´m not able to boot e.g. into EDL mode- I only can do something in FastBoot mode and meanwhile i´m a bit lost, cause i tried Recovery ROMS as well as FastBoot Roms and all of my flashing activities end up in the same scenario. Every flashing possibility i know is aborted.
Thx & cheers

Exact the same problem for me.
i have the same problem, some help would be great.

neo920768 said:
Hi, I have a serious problem here and maybe somebody has an idea.
Recently i upgraded via provided OTA update to 9.5.4.0 and everything seem to work fine, but I did afterwards a factory reset (via the menu of the phone) to the device- Mi account was deleted and bootloader is locked.
So i didn´t play at all with the mobile before.
I already requested now (after the problem occured) the unlock of the bootloader and got the feedback of Xiaomi that i can use now the Unlocker tool.
Unfortunately the device needs to have an MI account binding to use the Unlocker tool.
After the factory reset the device starts from scratch and i get the famous MIUI9 beginning screen, can choose the language and the region. Then the device try approx. 30 times to continue and end always with a message (only for some seconds): "Find Device closed unexpectedly". After approx. 30 times im ending up in the MI-Recovery 3.0 where i can choose REBOOT, WIPE DATA, CONNECT WITH MI ASSISTANT (PC-SUITE)
REBOOT: will do again 30 times the message: "Find Device closed unexpectedly"
WIPE DATA: starts from the choose of language and region again and it doesn´t matter which language i choose ends up in the MI-Recovery 3.0
CONNECT WITH MI ASSISTANT: ends up with the english version, that i can´t connect, but with the Chinese version, i can at least open the downloaded ROM 9.5.4.0 and start the flashing process which hang up immediately and doesn´t go beyond 0%. It ends up with some chinese messages i can´t read
FASTBOOT could be reached by pressing Vol- + On/Off, but doesn´t help with a locked bootloader i guess
So if anybody have an idea how to overcome the situation it would be quite helpful.
Thx
Click to expand...
Click to collapse
This seems to be a major bug I had it but resolved it by following this Test Point Method: http://en.miui.com/thread-1351514-1-1.html :good:
I used uBreakiFix to remove the back without chipping the did the process myself

@andril: Thx for the answer. Honestly from all what I read up to now, I expect such an answer, but I still have some questions:
Is this a bug, which is related to the latest upgrade only, or could this be happen also with older SW release?
Does the EDL testpoint method really work with the newest release I have?
Does it make sense to wait maybe for a new release to try the PC-Suite method again?
I don‘t fear to open the device, but want to avoid this of course if there is any possibility.
Thx&cheers

Gosh I was considering resetting my phone before selling on now I'm worried may have the same issue!
I don't think I'll be buying Xiaomi anytime soon.

@neo920768 it sounds bad but it works - @riz157 Not sure if it is a hardware bug after reset - I am glad i didn't do it after updating to the latest Global ROM

Just to give a feedback, that opening the device and flashing in EDL mode works good. Opening the device worked fine and you need to be careful about the fingerprint sensor, but after finishing you don‘t see anything on the device and everything works fine. Flashing with latest fastboot rom has also the small improvement, that you can choose between a lot of Regions, not only China.
Cheers and good luck to everybody
Thx

[SOLVED] Trying to unbrick phone from "This MIUI version can't be installed on this device" after failed OFFICIAL OS update.

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?!?

Xiaomi Mi 10T 5G Stuck on miui logo charging but cannot connect to pc

I really need help here my phone is is stuck on miui logo and it cant connect to pc i tried it on different pc’s but still cant connect but it still charges and i also tried changing the charging port but i still can't connect to pc
I can enter fastboot and recovery mode but my bootloaader is locked
I already did wipe data/ clear data but its still stuck on miui logo

In order to help, we need to know the previous steps before reaching that state.
If all is well, do a hard reset and flash the rom again, looks like you've wiped the system.
If you are using a custom rom, the only thing you need is to connect your phone in recovert mode, select apply from adb and install the rom with the relevant commands and names, If you are using a stock rom, you just have to follow the steps from official miui and install the rom that corresponds to your region and if you do not have the bootloader unlocked and you are using the stock rom and you have already tried to do a reset, I do not know how could I help.
Greetings and sorry for my english

What am I doing wrong?

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.