Develop Bugs

Mi Max bootloader issues

Hi guys.
I need help on a couple of different issues. I received my phone over the weekend - I got the 2/16 variant. I discovered I was on a vendor ROM and flashed the latest Global Stable. This worked fine, and I've had no issues.
I applied to unlock my bootloader yesterday and surprisingly recieved a text stating my request had been approved only a couple of hours later. When I've tried to unlock the bootloader though via mi unlock, it just gets stuck at 50% and can't verify my device.
I've installed the english and chinese version of mi suite in an attempt to ensure the correct drivers are installed, but given that I could flash via EDL method already, I'm pretty sure they are anyway. I then followed a guide on reddit last night whereby the recovery.img in a fastboot rom is replaced by that of the appropriate version of twrp and its all flashed via EDL method.
That worked, to an extent and I was able to boot into twrp but after I had given it the correct permissions I then attempted to boot into MIUI but it just hung at MI logo for a prolonged period - there was absolutely no movement or indication of it coming to life. Then reflashed again via EDL to the Global Stable and it's back to life.
So a few things I need help with:
How can I get this bootlaoder unlocked so I can install twrp an easier way e.g via ADB?
If I can't do that, what are my alternatives?
My phone takes at least an hour everytime I flash it via EDL - is that normal?

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

(RESOLVED) HELP PLEASE my Xiaomi BS3 is stuck in fastboot mode.

Hi. This is urgent since this phone is my personal one and I'm stuck here, its completely dead. I've read almost every thread in this section and tried the commands, and use the files they had but they do not work... anyways, here's the situation:
Last update ( KLEN2203050OS00MR1 ) hardbricked my phone. It was literally dead, I had no firmware, or ROM whatsoever. I already took it to a verified Xiaomi store and they gave it back to me (they didn't do much tbh just fixed the bootloop). I flashed with with EDL mode and now bootloader is unlocked and I can access recovery mode. When I try to flash, I keep getting the same error with the next files: system, vendor, product, and odm -they are .img files. And to add, I have another error saying " FAILED (remote: 'Partition not found') ". I've read multiple posts and threads that they were able to fix that issue with " fastboot flash fastboot " or something like that. I tried the command again days ago and tried to flash again, but no luck. I am trying to install a stock ROM. My phone is a Xiaomi Black Shark 3 Qualcomm Snapdragon 865. I believe I have the global version.
I would really appreciate any help really, since I've been dealing with this for 2 weeks now, and taking my phone to the verified store to fix it will take weeks and it's very expensive...

have you try flashing with qfil rom?

Bootloop with acces to recovery and fastboot

After the S20 screen screen died I decided to go Poco X3 pro then I was told that it dies randomly and after alot of googling the Mi 10T seemed like the perfect deal to ever exist for me so I went on and bought one yesterday so far so happy I won't lie it feels so so good no clue what all the trash talk about its screen coming from S20 with wqhd+ always enabled I see no difference what so ever with mi 10t but then again am nearly blind (sad fact lol) after I got home I did a factory reset from the settings (no mi account was logged) I had a second hand note 9 pro and I got traumatized cuz I did a factory reset with the last owner acc linked to it and never used the phone ever after thanks to the mi lock xD
Dry I get off topic alot forgive me alright now the the phone is back to factory status the sound/mic/Bluetooth earphones/wired earphones no longer working I was like am sure this little miui 13 update notifications will solve that no problems and I went on to download it after it finished I did it and it caused the phone to go into a bootloop and it occasionally end the bootloop through going to recovery by it self and not doing anything cuz it to restart into bootloop again (am telling u guys this phone is HAUNTED) alright after crying to blindness in the shower I go for round 2 now armed with Google/YouTube/XDA and Reddit I was like yea boi certainly you will fix this hard earned phone
I went to try
-wipe data from recovery then reboot
-remove SIM tray
-put a SIM card
-remove the SIM card
-wait for as far as the black screen past the mi with 3 loading dots go (led light on) and call it
-safe mode
-unlocking back cover and unplugging the battery (friend halped me with emotional support cuz that part scared the living out of me) WHY THEY MAKE BATTERY SO HARD TO UNPLUG
-fastboot command every single one I could find
-leaving it reboot for 5 hours
Conclusion: non of the solutions above worked for me
So I went to cry in the shower again and came back for round 3
Now I went on to download every Xiaomi mi 10t driver I could find / Qualcomm drivers / miflash tool (every single version) / miflash tool pro ( the one with black logo) / Xiaomi tool V2 by Francisco I think (forgive me if I name u wrong Francisco cuz it's been a tough day) / mipc suit assistant / every mi 10t ROM recovery or fastboot I could find ( I didn't have a clue what the difference between them was but I learned it along the lol journey ).
After installing everything I started testing
And the Results are as follow:
-miflash tool with every ROM except for one : erase boot error / erase is not allowed in lock state
I still can't understand this error cause the ROMs I downloaded re supposed to be official not custom ROMs or something and re supposed to be able to flash with locked bootloader without mi auth specially that my phone does not have mi account linked to it.
One ROM tho did give me flash success in like 1 second after clicking flash but nothing happens and nothing changes.
-miflash tool pro the phone gets recognised and show me to click flash recovery but clicking it make nothing happen while in YouTube it shows a second window to proceed with flash for other people
-clicking the flash_all.bat and all the other different flash_xxx.bat blinks a CMD window and nothing happen
-flashing with ADB by all different methods results in all kind of errors and non works
-mi pc suit assistant doesn't even detect the phone in recovery but when I put it in fastboot it show screen saying that I should back up then proceed to fastboot but rebooting back to fastboot make nothing happens and trying to click back or the flash button in the assistant shows nothing (different version of mi assistant shows device not supported when I start it in fastboot and shows nothing in recovery)
-Xiaomi unlock tool V2 by the one who was so so so close from saving me Francisco him self this one unlike the other apps do go much further after clicking the option for bricked phone (cuz the other option for modding require unlocked bootloader) and choosing the redmi k30s ultra appollo (cuz no mi 10t on the list) and letting it download the ROM it started flashing it (OMG ITS A SIGN THAT AM GOING IN THE RIGHT PATH) the phone shows a loading screen that freez at 4.99% but it goes further later on (same thing do happen for other guy on YouTube but he end up with better result then I did in the end) and once it reaches 90% or 91% am not sure cuz it happens so fast the Xiaomi unlock tool V2 shows error in the laptop and the phone goes back into its never ending bootloop version of ouroboros (Francisco if u reading this please feel free to add option to load other ROMs then the one Ur app download to it self to flash cuz I felt like one of the ROMs I have could maybe work and someone else may be in the same situation one day too)
nothing work for me but I have a good feeling about miflash tool if I know what causing the erase not allowed in lock despite the ROM being stock and does not need unlocked bootloader.
I took the phone to a Xiaomi service centre but they refused to provide any help saying that my phone was never supposed to exist in my country and is only sold in Europe and they can't provide any help for me, they treated me the same with the issue with my redmi note 9 pro when the phone got mi lock despite showing the box and all its paper, the original owner purchase paper and giving them my national ID
If someone have a solution please tell me cuz I truly need Ur help and have no other options and no clue what to do at this point am completely a newbie at this never flashed a ROM before today and never had such an issue and sorry again for making this long but I truly wanted to explain everything I tried and provide as much information to the issue as I can
XDA Geniuses my phone fate is at ur hands if u choose to help me
EDIT: I was so nervouse I forgot to say that the phone is MI 10T and fixed some typos despite so many more exist cuz my English suck

It's been months now and am still trying but can't get the phone to work and no one seem to know a solution to the issue am facing

Little update after months of trying something popped out now when I flash the phone with MiFlashPro (the one with black logo) the phone make it to 90% then reboot but it's still bootlooping the same the only difference now that the phone MIUI version actually changed it went from 13.0.6 to 13.0.8 so since the version is changing something is changing wish did not happen before now am gonna try the older versions and see if it's even possible to downgrade thro recovery flash or not and then will try the miui12.5 since that's the last it been working fine on

Yep the MiFlashPro does not let u flash old ROM and won't allow u to downgrade
Does anyone know of a way to side load recovery ROMs ?? At this point I should go try and apply for a phone repair certificate then apply for a job or internship in Xiaomi repair center so I can get access to the EDL so I can revive my phone

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.