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?

Troubles with booting TWRP via adb

Just as the title says, I'm having trouble trying to boot TWRP via adb.
As a quick overview, this phone arrived with an unlocked bootloader from the seller I bought it from at AliExpress. Because of that, I decided to flash Pixel Experience 8.0. I remember back then that it gave me a few issues as well when it came to trying to boot TWRP via adb but somehow managed to do so.
Ultimately, I was able to run the rom without a problem and it was smooth sailing from there. Fast forward to now, I thought it was time that I updated to PE 9. Again, I'm having issues trying to do the same thing. If you're wondering why I don't have TWRP installed, it's because I didn't want to root my phone
due to issues that's connected to Fate Grand Order. I remained unrooted, which meant that I had stock recovery.
My biggest problem is the (Command Write Failed [Invalid Argument]) text when trying to boot TWRP. If it's not that, then it's stuck at "Waiting for device." Both situations lead to "Press any key to shutdown" at the top left corner of the fastboot screen.
Any thoughts?

1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2

YasuHamed said:
1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after work.

Question Hard bricked phone several months after installing a custom ROM

TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
After getting phone hard bricked for the first time, on my second attempt to load a custom rom, the phone hard bricked again.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
Click to expand...
Click to collapse
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.

I don't know a lot about bricks in general but i think you are supposed to format data after you flash the recovery because that's what i did after installing arrow os but i don't know how would that cause a hard brick.

PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30

regedit12345 said:
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
Click to expand...
Click to collapse
The problem is I have another exact device which is running the latest version of PE fine.

jylee1997123 said:
The problem is I have another exact device which is running the latest version of PE fine.
Click to expand...
Click to collapse
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.

regedit12345 said:
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
Click to expand...
Click to collapse
I think there is some confusion here.
Are you referring to the first hard brick? No OTA update is performed because it is running PEX which does not support OTA updates.
If you are referring to the second hard brick, the phone is never in PE firmware at all. The moment I tried to flash PE rom, the phone got hard bricked with these steps. ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
2 Devices
1) My personal device (POCO F3 Alioth) - Working fine with current latest stable PE
2) Her device (POCO F3 Alioth) - HardBricked, EDL when flashing with these steps ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )

jylee1997123 said:
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
Click to expand...
Click to collapse
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues

Zainullahk1234 said:
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Click to expand...
Click to collapse
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?

Try flashing aospa.

jylee1997123 said:
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Click to expand...
Click to collapse
hmm i dunno then pe works perfectly on my x3 pro
are you sure your using the correct firmware?
try flashing miui firmware over it and booting (cause mabye the oss vendor is the issue)
or just sell your f3 and get the f4 once it comes out (looks to have snapdragon 8 gen 1!)

Try installing CrDroid, follow their installation steps, they work very well

I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again

usmanjavid said:
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
Click to expand...
Click to collapse
You definitely haven't tried PPUI

regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
LOL
dont mention that buggy mess

regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
i tried installing this instead of arrow os and i couldn't even boot into it it would just go back to miui

Zainullahk1234 said:
LOL
dont mention that buggy mess
Click to expand...
Click to collapse
I have tried all the A12 roms including syberia and arrow and by far this is the best rom. The maintainer of the rom is dev himself and very active and responsive on the telegram grp.
[Discontined][12.0][alioth/aliothin] Pixel Plus UI Poco F3 / Xiaomi Mi 11X / Redmi K40
This tread was discontined as far as I dropped support of PixelPlusUI Project. Thanks to all users and supporters who was Interested to project. Future Development for Poco F3 will be according to own new project - VoidUI Project Github...
forum.xda-developers.com

Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though

i have seen pixel extended that got his thread closed because at shutdown the phone bricked so it really is the roms fault

jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
Pixel extended= bad
pixel experience= amazing

jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
That's why I suggest using CrDroid, mostly because I haven't failed any installation following their installations steps, the ROM being stable and having good customizations is a perk that comes with it

Can't install custom ROM on Redmi Note 8 on MIUI 12.5

I had some problems with my phone, it was laggy and i saw that pixel experience was something great and worth the flash, so i started my research and tried installing it. I was running on MIUI 11 at that time and i somehow managed to install TWRP recovery to the phone and flash the pixel experience, bu the problem was that the pixel experience ROM didn't read my SIM card, didn't see my Wi-Fi networks and restarts didn't help. I followed a tutorial from youtube step by step, but the video was a little old. After this failed attemp i flashed back to MIUI 11 a couple of times, each time repeating the procces and trying with new ROMs. After some time i read that i need to run the latest MIUI in order to not have any problems with Network and Wi-Fi. I started the process again, adb and fastboot installed, bootloader unlocked and USB debugging on. I tried two methods and they both failed. First was using TWRP recovery, wich after flashing didn't work, if i was holding power and volume up button after flashing, my phone would give me the system was destroyed message. The second method was flashing the pixel experience using cmd and it also failed, device was rebooting back to MIUI after flashing, and if i was holding the power and volume up button, again it told me that the system was destroyed. I watched multiple videos and followed instructions from multiple websites but nothing was working for me. I don't want to give up on installing this ROM, but i seem to fail every time. If anyone could help me, or if anyone went through the same problem, please answer to this post, i will be very thankfull.

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.